I know how flatpaks are updated, thanks a bunch. Not that it matters particularly on Bazzite these days, because Bazaar will do that for you on the gui, too. Gear Lever will handle your appimages, if you're lucky. We could have a conversation about how much sense it makes to have updates happen in four different places and how much sense it makes to advise people to stop using their pre-bundled "update everything" script and start updating each of those separately to avoid a troublesome updated driver as a permanent solution.

In any case that's not the only part of your software that comes with a system update. The list of end-of-life features and warnings I see reported on OS updates has been steadily growing as my install ages, which has been interesting to see simmer, given all the "it's foolproof" talk about immutable/atomic distros on the internet. I have to assume some of those will get sorted out in future updates, but so far the list has been moving in the wrong direction.

Honestly, when I do have the time and motivation I will likely just rebase to a whole different branch and go from there depending on what fixes itself or breaks. I assume that will get rid of a bunch of stuff.

But that's already waaay past what an average user should have to do to their OS. Especially in the time this install has been live without a rollback or rebase (and it's had some, because it's not the first time it breaks). I'm not even sure Bazzite shipped a broken update. It could just be an issue on KDE's side. Or on Nvidia's side. Who knows. Being able to roll back my system to a point where it worked is not a fix, it's a troubleshooting step. Having to troubleshoot IS the problem in itself.

I mean, unless you broke something yourself, I suppose. But you're also supposed to not be able to do that in an atomic distro, if you believe what people will tell you.

For the record, as I told someone else, I didn't choose Bazzite because it was an atomic distro (in fact it's kind of a pain in the ass that it is, KDE really doesn't like it when you try to customize stuff in one of those and doesn't handle it gracefully at all). I chose it because I had a hell of a time finding a distro that would pick up my sound hardware properly (sound on Linux is yet another rabbit hole) and still have proper HDR and VRR support with my display setup. The list of distros that did not do both of those things at once before I landed on Bazzite includes Manjaro, Ubuntu, Mint, Fedora Workstation and a couple of others I didn't test for long enough to remember.

That's a lie. Manjaro aaaalmost got there. It worked for a while. I kinda forget what broke that made me try something else.

You can see how that entire ordeal is... not mainstream-friendly in aggregate, though, surely.

It's probably worse than it's been, less bad than people around here think.

One thing MS does is they have a TON of silent channels and branches, so every release they do is a rolling release. As a result, when you see in the news that they fucked up again and messed up a bunch of something somewhere it tends to be relatively contained still. I think the latest was a bad patch breaking a bunch of stuff that required a couple of emergency patches and I think there may be more to go.

It's 100% not good, and it almost certainly affected a lot of machines, but it probably got stopped from spreading further. If they had a signed driver update break their entire desktop interface in an update sent to every user they'd be (rightfully) crucified endlessly.

I get that there is a massive discrepancy of resources at play, but that doesn't make it better from the end user perspective. I've been saying for years that the Linux community keeps saying that "you can choose the distro you like" is a feature, but it isn't. Desktop Linux should be one thing. A couple, max. Contributions should be way more centralized and pool resources, like they are on the kernel. Distro choice is an anti-feature and a massive waste of resources.