my brain compelled me to make this shitpost
character by @prahou
@ammoniumperchlorate @prahou rust and mastodon belong on the left
@newt @prahou @ammoniumperchlorate
Okay, buzzkill, Gentoo, Graphene and Nix too 😏
@m0xee @prahou @ammoniumperchlorate Nix is split, there are forks afaik. But you're right. Also, sourcehut and sway go there too.
@newt
Agreed! I'm fine with both (and you're using Nix 😜), but we aren't picking darlings here, right?
I's probably add P9 and LFS to replace Nix and Gentoo and… I dunno, dwm — in addition to i3, to replace Sway.
@prahou @ammoniumperchlorate
@m0xee @newt @prahou @ammoniumperchlorate You all haven't met enough tech normies.
@j3rn @newt @prahou @ammoniumperchlorate
> tech normies
Most of the time I just laugh the remarks about "tech normies" off, but then I stumble upon something like this…
OMG, you need the latest top of the line multicore ARM chip with 36 gigabytes of RAM on it to be more productive… writing code? So your "tools" won't slow you down? This world is doomed! DOOMED!!! 😱
@m0xee @j3rn @prahou @ammoniumperchlorate oh man this gives me nightmares. I had to buy a new laptop because 16G (well, more like 15G because VRAM) wasn't enough to run Slack and build code at the same time. I'm being serious here.
Follow
@newt @j3rn @prahou @ammoniumperchlorate
> wasn't enough to run Slack
But that is exactly the product of developers like that — who need 36 gigabytes or RAM to be productive 🤣
We've come full circle here, the system is reproducing itself.
@newt@stereophonic.space
@m0xee @j3rn @prahou @ammoniumperchlorate I'm not sure I would want to call the people behind Slack "developers". They are more of retarded shit-for-brains apes.
@m0xee @newt @j3rn @ammoniumperchlorate
> But that is exactly the product of developers like that — who need 36 gigabytes or RAM to be productive 🤣
it seems these days it's "cheaper" to buy more hardware to throw at a "problem" than it is to retool and optimize the "problem". i can relate to newt. i had previous job where the laptop they sent (mac) would not allow me to pair-program with colleagues over slack-hangout or whatever it's called because i started paging to disk quickly running the development stack.
it's been over for a while. i could be wrong.
> But that is exactly the product of developers like that — who need 36 gigabytes or RAM to be productive 🤣
it seems these days it's "cheaper" to buy more hardware to throw at a "problem" than it is to retool and optimize the "problem". i can relate to newt. i had previous job where the laptop they sent (mac) would not allow me to pair-program with colleagues over slack-hangout or whatever it's called because i started paging to disk quickly running the development stack.
it's been over for a while. i could be wrong.
@jae @j3rn @ammoniumperchlorate @m0xee
>it seems these days it's "cheaper" to buy more hardware to throw at a "problem" than it is to retool and optimize the "problem".
Except this doesn't work. My workstation is Threadripper 3970 (32 cores/64 threads) with 128G of RAM, and Slack is still annoyingly slow as fuck. Today it's the only Electron application on my computer and I hate it with all my guts. It doesn't matter how good your hardware is, this shit will always just be slow due to the sheer amount of complexity it contains.
>it seems these days it's "cheaper" to buy more hardware to throw at a "problem" than it is to retool and optimize the "problem".
Except this doesn't work. My workstation is Threadripper 3970 (32 cores/64 threads) with 128G of RAM, and Slack is still annoyingly slow as fuck. Today it's the only Electron application on my computer and I hate it with all my guts. It doesn't matter how good your hardware is, this shit will always just be slow due to the sheer amount of complexity it contains.
@newt @ammoniumperchlorate @j3rn @m0xee
> Except this doesn't work. My workstation is Threadripper 3970 (32 cores/64 threads) with 128G of RAM, and Slack is still annoyingly slow as fuck. Today it's the only Electron application on my computer and I hate it with all my guts. It doesn't matter how good your hardware is, this shit will always just be slow due to the sheer amount of complexity it contains.
i truly can relate. before i parted it out for being more mobile (nomadic) i had a 5950x/128b/4tb system that anytime i ran slack or some other electron trash (looking at you signal desktop) i'd watch the visualization in my monitoring climb quickly vertical, sustain, then leak more upwards.
it may be out of scope, but have you looked into any tui apps that interface with slack? i recall there being something that worked. at least it worked for messages, not video, voice, screen share.
these days i have what most "modern developers" would consider an old laptop (2018 t480 4c/8t, 32gb, 1tb ssd) and for the investment in it (maybe total of 300$ usd)
it does the job to get tasks and engineering work done. although it's like driving a ford pinto with 3 wheels to some of these newer era developers.
> Except this doesn't work. My workstation is Threadripper 3970 (32 cores/64 threads) with 128G of RAM, and Slack is still annoyingly slow as fuck. Today it's the only Electron application on my computer and I hate it with all my guts. It doesn't matter how good your hardware is, this shit will always just be slow due to the sheer amount of complexity it contains.
i truly can relate. before i parted it out for being more mobile (nomadic) i had a 5950x/128b/4tb system that anytime i ran slack or some other electron trash (looking at you signal desktop) i'd watch the visualization in my monitoring climb quickly vertical, sustain, then leak more upwards.
it may be out of scope, but have you looked into any tui apps that interface with slack? i recall there being something that worked. at least it worked for messages, not video, voice, screen share.
these days i have what most "modern developers" would consider an old laptop (2018 t480 4c/8t, 32gb, 1tb ssd) and for the investment in it (maybe total of 300$ usd)
it does the job to get tasks and engineering work done. although it's like driving a ford pinto with 3 wheels to some of these newer era developers.
@jae @j3rn @ammoniumperchlorate @m0xee
>have you looked into any tui apps that interface with slack?
I'm literally two inches close to setting up a Slack-IRC bridge and just using my IRC client, like God intended. Unfortunately, my coworkers like using some more advanced features of Slack that do not map well onto IRC. Like voice calls, for example.
Another way would be to set up Slack for Android inside something like Waydroid, because apparently the Android version consumes a lot less resources. Because phones, you know.
>have you looked into any tui apps that interface with slack?
I'm literally two inches close to setting up a Slack-IRC bridge and just using my IRC client, like God intended. Unfortunately, my coworkers like using some more advanced features of Slack that do not map well onto IRC. Like voice calls, for example.
Another way would be to set up Slack for Android inside something like Waydroid, because apparently the Android version consumes a lot less resources. Because phones, you know.
@newt @ammoniumperchlorate @j3rn @m0xee
> I'm literally two inches close to setting up a Slack-IRC bridge and just using my IRC client, like God intended. Unfortunately, my coworkers like using some more advanced features of Slack that do not map well onto IRC. Like voice calls, for example.
the bridge approach is a good one except for the advanced features as you mentioned. i had experimented with this in matrix, but i really don't bother with that system anymore. i found a few golang bridges on micr0$hub that might work.
> Another way would be to set up Slack for Android inside something like Waydroid, because apparently the Android version consumes a lot less resources. Because phones, you know.
if it can access the input/output of your mic/camera/etc to satisfy your coworkers needs this feels like the better approach. i've seen some do this with signal, although i don't recommend anyone use it.
> I'm literally two inches close to setting up a Slack-IRC bridge and just using my IRC client, like God intended. Unfortunately, my coworkers like using some more advanced features of Slack that do not map well onto IRC. Like voice calls, for example.
the bridge approach is a good one except for the advanced features as you mentioned. i had experimented with this in matrix, but i really don't bother with that system anymore. i found a few golang bridges on micr0$hub that might work.
> Another way would be to set up Slack for Android inside something like Waydroid, because apparently the Android version consumes a lot less resources. Because phones, you know.
if it can access the input/output of your mic/camera/etc to satisfy your coworkers needs this feels like the better approach. i've seen some do this with signal, although i don't recommend anyone use it.
