I just recently installed Bazzite and I have to say that your experience was unusual. Installing apps from the built in Software Center (it’s not really an app store, because it’s not really a store), just worked for me.
But, I’ll agree with you that Linux isn’t quite ready for mass adoption. Currently I’m tracking an nVidia bug that results in my GPU locking up when doing pretty normal things. The bug was reported 3 weeks ago, and is affecting a lot of people with more than 1 monitor, but still hasn’t been fixed. I’m also tracking 2 annoying but not system-crashing bugs. Plus, there’s another behaviour that happens daily that is annoying and I haven’t had the time to track down.
Mostly, these are “chicken and egg” things. The nVidia bug was allowed to happen and wasn’t fixed quickly because there aren’t enough Linux users for nVidia to bother to fully test their things on lots of different Linux configurations before releasing them, or to make it an all-hands-on-deck emergency when they break. If there were more users, the drivers would be better. But it’s hard to get people to migrate to Linux because there are frequently buggy drivers. Same with other drivers, and other commercial software. People don’t switch because it’s glitchy, it’s glitchy because there aren’t enough users for companies to properly invest in fixing things, that makes it glitchy, so people won’t switch.
Having said that, the thing that prompted me to install Bazzite was that I was getting BSODs in Windows and I wasn’t sure if it was a driver issue or a hardware issue. It turned out to be bad nVidia drivers… but they were fixed in days, not weeks. So, it’s not that things don’t break in Windows, it’s just that it’s a bigger emergency when they do break.
I’m not going back to Windows any time soon. Despite the issues I’m having, there are some parts of the system that are so much better than Windows.
Like, people complain about Linux having a bad UI, but have you ever tried to change low-level network settings in Windows? You start in a windows 10 or 11 themed settings app. If the thing you’re trying to change doesn’t show up there you have to click to open a lower-level settings app, this one styled in a Windows XP UI. And if that’s not where the setting lives, you have to open up a lower-level thing that is using the Windows NT / Windows 3.1 interface.
Or, anything involving using a commandline. Windows does actually support doing a lot of things using the “DOS prompt” but that thing feels like a Fisher Price toy compared to a real shell. Even the “power” shell is a janky mess.
Or, any time you have to touch the registry. Only an insane person would prefer to deal with making changes there vs. making changes in a filesystem where you can comment out values, leave comments explaining what you did, back up files, etc.
But, while Linux isn’t quite there for the end-user, it’s getting closer and closer. Really, all that’s needed is enough people taking the plunge to make it a higher priority for devs. It could be that Microsoft deciding that Windows 10 machines that are not capable of running Windows 11 should just be thrown out will convince enough people to try Linux instead. Linux might not yet beat Windows for the average end user, but the annoyances associated with Linux vs. a machine you just have to throw away? That’s an easy one.
Yeah, I get it’s unusual and it sucks it happened. I honestly would have been less upset if it was a driver issue or something like that. I at least could have looked at dmesg logs or something to try and figure out what was going on. I’m new to GUI Linux, so I had no idea where to start with this one. I think this was more frustrating than a driver issue or something similar for me because I would expect installing applications from the built in repositories to be something that “just works”.
Hopefully as more people move over to Linux distros, we will get more people that donate to them as well so more dedicated developers can be hired to work on such things. I know it will get there one day, and it’s already so much better from when I last tried gaming on Linux back in the early 2010’s. Hopefully the full release of SteamOS will truly bring about the age of Linux desktop.
If Steam OS getting a wider release happens around the same time as Windows 10 hitting end-of-life, that could be a game-changer.
I know what you mean about it being frustrating when flatpak apps don’t work right though. I had an app that would just start to open and die, no error message, no feedback, just it started to open then closed. Because I was new to Flatpak I didn’t know how to poke at it. But, then I discovered how you can run flatpak apps from the commandline, and when you do that you get access to flags and you get error messages you can read. But, if you’re just some dude/dudette who wants to sit down and run an app and it doesn’t work, that kind of behaviour is ultra frustrating.
The problem is that there’s still a lot of flux when it comes to packaging and running Linux apps. There’s the old way – debs and rpms. There’s flatpaks, there’s the snap store, there’s homebrew, there’s mise and of course there are manual installs and/or building from source. Each one’s a bit different and has its own benefits and drawbacks. And, standard things like showing an error message that helps you sort out the problem when things break isn’t universally handled in a clean way.
I just recently installed Bazzite and I have to say that your experience was unusual. Installing apps from the built in Software Center (it’s not really an app store, because it’s not really a store), just worked for me.
But, I’ll agree with you that Linux isn’t quite ready for mass adoption. Currently I’m tracking an nVidia bug that results in my GPU locking up when doing pretty normal things. The bug was reported 3 weeks ago, and is affecting a lot of people with more than 1 monitor, but still hasn’t been fixed. I’m also tracking 2 annoying but not system-crashing bugs. Plus, there’s another behaviour that happens daily that is annoying and I haven’t had the time to track down.
Mostly, these are “chicken and egg” things. The nVidia bug was allowed to happen and wasn’t fixed quickly because there aren’t enough Linux users for nVidia to bother to fully test their things on lots of different Linux configurations before releasing them, or to make it an all-hands-on-deck emergency when they break. If there were more users, the drivers would be better. But it’s hard to get people to migrate to Linux because there are frequently buggy drivers. Same with other drivers, and other commercial software. People don’t switch because it’s glitchy, it’s glitchy because there aren’t enough users for companies to properly invest in fixing things, that makes it glitchy, so people won’t switch.
Having said that, the thing that prompted me to install Bazzite was that I was getting BSODs in Windows and I wasn’t sure if it was a driver issue or a hardware issue. It turned out to be bad nVidia drivers… but they were fixed in days, not weeks. So, it’s not that things don’t break in Windows, it’s just that it’s a bigger emergency when they do break.
I’m not going back to Windows any time soon. Despite the issues I’m having, there are some parts of the system that are so much better than Windows.
Like, people complain about Linux having a bad UI, but have you ever tried to change low-level network settings in Windows? You start in a windows 10 or 11 themed settings app. If the thing you’re trying to change doesn’t show up there you have to click to open a lower-level settings app, this one styled in a Windows XP UI. And if that’s not where the setting lives, you have to open up a lower-level thing that is using the Windows NT / Windows 3.1 interface.
Or, anything involving using a commandline. Windows does actually support doing a lot of things using the “DOS prompt” but that thing feels like a Fisher Price toy compared to a real shell. Even the “power” shell is a janky mess.
Or, any time you have to touch the registry. Only an insane person would prefer to deal with making changes there vs. making changes in a filesystem where you can comment out values, leave comments explaining what you did, back up files, etc.
But, while Linux isn’t quite there for the end-user, it’s getting closer and closer. Really, all that’s needed is enough people taking the plunge to make it a higher priority for devs. It could be that Microsoft deciding that Windows 10 machines that are not capable of running Windows 11 should just be thrown out will convince enough people to try Linux instead. Linux might not yet beat Windows for the average end user, but the annoyances associated with Linux vs. a machine you just have to throw away? That’s an easy one.
Yeah, I get it’s unusual and it sucks it happened. I honestly would have been less upset if it was a driver issue or something like that. I at least could have looked at dmesg logs or something to try and figure out what was going on. I’m new to GUI Linux, so I had no idea where to start with this one. I think this was more frustrating than a driver issue or something similar for me because I would expect installing applications from the built in repositories to be something that “just works”.
Hopefully as more people move over to Linux distros, we will get more people that donate to them as well so more dedicated developers can be hired to work on such things. I know it will get there one day, and it’s already so much better from when I last tried gaming on Linux back in the early 2010’s. Hopefully the full release of SteamOS will truly bring about the age of Linux desktop.
If Steam OS getting a wider release happens around the same time as Windows 10 hitting end-of-life, that could be a game-changer.
I know what you mean about it being frustrating when flatpak apps don’t work right though. I had an app that would just start to open and die, no error message, no feedback, just it started to open then closed. Because I was new to Flatpak I didn’t know how to poke at it. But, then I discovered how you can run flatpak apps from the commandline, and when you do that you get access to flags and you get error messages you can read. But, if you’re just some dude/dudette who wants to sit down and run an app and it doesn’t work, that kind of behaviour is ultra frustrating.
The problem is that there’s still a lot of flux when it comes to packaging and running Linux apps. There’s the old way – debs and rpms. There’s flatpaks, there’s the snap store, there’s homebrew, there’s mise and of course there are manual installs and/or building from source. Each one’s a bit different and has its own benefits and drawbacks. And, standard things like showing an error message that helps you sort out the problem when things break isn’t universally handled in a clean way.