This is the real issue IMO, framework mainly appeals to the environmental crowd and economical crowd. Problem is buying used corporate workstations is way better for both these markets + it doesnt even seem like the motherboard upgrades are much cheaper than just buying a new used laptop. Maybe with terrible ssd prices the calculus changes, but you still need to upgrade ram on a new board anyway. Hardware just doesn’t improve on the 2-4 year timescales to justify this anymore.

That’s interesting since you were already using slack, did you just switch due to network effect or are there additional features in discord?

Can it do drop in/drop out VoIP rooms like mumble?

Discord was originally a replacement for teamspeak/mumble and it’s how most people I actually know still use it. It was “nice” because you didn’t need to set up your own server. Using it as a replacement for irc came later. Image support in chats is nice, but I really only use it for the voip chat rooms.

This doesn’t make sense because the reverse would be true, and it’s not. If they were so different an explosion in server demand wouldn’t strongly affect consumer products.

The Dynamicland website reminds me of the worst of the 00’s, it really turned me off to the whole project

Sourcehut is really the only step between just using an ssh server and something like forgejo that I know of.

Never had as bad an experience with Linux as on a Macbook, and that includes Dell laptops in the early '10s. Sound doesn’t work, sleep doesn’t work either. Beyond that the keyboard is screwed up and double types all the time, which is totally unreasonable on a laptop ~5 years old.

Especially when most games that’ve come out this year run like shit, and a new graphics card is nearly a rent payment

technically libreoffice exists, they really need to fix office comparability though

More than 5 years old includes all the major live service titles at this point, back in the day people would be hopping to whatever new COD/Battlefield just came out, which would lock that metric to 2-3 years max. Since Moore’s law is long dead at this point the technology just doesn’t improve much year over year, and it’s hard to sell a new minor iteration on a game without flashy visual upgrades, the old model just doesn’t really make sense anymore.

I think this is the most important aspect of Linux accepting more rust contributions. More and more existing maintainers are aging out, and people just don’t learn or want to build large applications in C anymore. From what I understand companies doing proprietary kernel development have largely made the rust transition for new code at this point, so fewer and fewer systems level programmers will be used to C (and C++ over time) for these tasks. Existing maintainers pressure against rust development could become a threat to the long term viability of the kernel.

It seems like since my generation had “If you put something on the Internet it’ll be there forever” drilled into us as kids, many of us feel entitled to “the internet” preserving our data for us. Most people don’t realize how much labor and resource usage goes into preserving data forever.

What’s your setup for self hosting? Do you use a vps or host on your own network?

I feel like I did at one point, but I should probably try again

Yeah I’m not super surprised… It used to work well when I bought it back in '17 but it’s become worse and worse with updates.

I’m not a home theater power user, but this is good info to make sure my setup is future proof for when I finally get a new TV. All these different standards get really confusing.

One specific example I encountered was ndarray. I couldn’t figure out how to make a function take an array and an arrayslice without rewriting the function for both types. This could be because I’m novice with the language, but it didn’t seem obvious. I ended up giving up after trying to dig through the docs for a few hours and went back to C++.

Maybe for your use cases that’s OK, but there are many situations where the size and ease of upgrading provided by shared libraries is worthwhile. For example it would suck to need to push a 40+ GB binary to a fleet of systems with a poor or unreliable internet connection. You could try to mitigate this sort of thing by splitting the application up into microservices, but that adds complexity, and isn’t always a viable tradeoff if maximizing compute efficiency is also a concern.

In my understanding, you can’t interface with the C abi without using an unsafe block.