That’s fair, but by that accounting it’s probably better to say that when you buy something for $10, $1 goes to the worker, $1 goes to the company, and $8 goes to other companies who then pay their workers, etc.

Of course they exist, but they’re likely not factored in to the cost of the good you’re purchasing. The worker isn’t going to make any more money if you buy a product. (Unless there’s a commission, I suppose)

When you buy something from a big corporation, unless you’re tipping (and frequently even if you are tipping) usually $0 goes to the workers. It all goes to the company.

The biggest thing for me is that a lot of them don’t officially support dual-booting on one disk, e.g. Kinoite. I like to have multiple distros installed so I have a fall-back. I love using Tumbleweed for gaming, but I’d love to use an atomic distro for my development work. But I don’t want to use one in an unsupported way, as that defeats the point in my eyes.

Or “Invasion of Privacy” Policy

Yeah I was pretty surprised. There are still some frustrations now and then but the Nvidia driver has gotten much closer to AMD lately. There’s even an open driver being developed.

If I’m reading the merge correctly, the Wayland bugs aren’t fixed, PCSX2 just added enough workarounds to consider things working.

Every time I hear about muskrat these days I can’t help but think of Chang. I wonder when the amnesia arc is going to start.

I haven’t done it in a bit, but you should be able to do Windows startup repair from a USB (possibly a Windows install USB), which I believe can restore the bootloader. I’d recommend disconnecting all drives other than the Windows one when doing the repair.

Yeah this is a big part why I’m very skeptical of Signal. It feels a lot like Ubuntu’s snap store, it’s technically open but you can’t really interact with the main corporate controlled ecosystem.

Did you read the article? It’s talking primarily about how this could be really good for consumers.

I think “speed up Wayland development” isn’t quite right, tho it will probably feel that way to end user. It’s about getting experimental protocols into the hands of users in a formalized manner while the stable protocol is still being forged. This already exists in certain forms e.g. HDR support being added before the protocol is finalized, but having a more formalized system is probably pretty helpful for interoperability, e.g. apps having to work with different DE’s.

My biggest is concern is whether there’s a possibility this will actually slow down Wayland development by pulling attention away from the stable Wayland protocols in favor of Frog Protocols. But hopefully the quicker real world usage of the new protocols will bring more benefits than the potential downside.

If you’re worried about the lack of Unix-style permissions and attributes in NTFS

I’m pretty sure Linux still uses Unix-style permissions in NTFS, which causes issues when Windows tries to use its own permission system on the same partition.

In 2027 the current iteration won’t be legally able to be sold in the EU, since the EU will require portable devices to have easily replaceable batteries. (Which the Steam does not qualify for due to needing a heat gun). So an upgrade is almost certainly planned by then.

I feel like there’s also the point that on Mac OS a lot of stuff “just works” because everything else just doesn’t work at all. I have a number of things that just aren’t going to work at all on Mac. Linux is obviously much more permissive, which leads to a lot more kinda working stuff that just wouldn’t work at all on Mac.

The compositors are the ones doing a lot of the protocol development. They want to have WIP versions so they can see what issues crop up, they’ve been making versions all doing. Now, I agree that it is slowing things down, but it’s more of just an additional thing that needs to get done, not so much a chicken and egg problem.

Wine and Proton have actually put a ton of work into Wayland support, it’s very far along. I wouldn’t be surprised for Proton to have a native Wayland version soon.

Also XWayland has many limitations as X11 does.

If an app has only ever supported X11, then it probably doesn’t care about those limitations (the apps that do care probably already have a Wayland version). And if an app doesn’t care about the extra stuff Wayland has to offer, then there’s not really a reason to add the extra support burden of Wayland. As long as they work fine in XWayland, I think a lot of apps won’t switch over until X11 support starts dropping from their toolkit, and they’ll just go straight to Wayland-only.

Programming languages is way too broad a category. There’s a lot of variation in both power and difficulty.

I think there’s a difference when the source material isn’t great. IIRC Forest Gump is another example.