- NTSync coming in Kernel 6.11 for better Wine/Proton game performance and porting.
- Wine-Wayland last 4/5 parts left to be merged before end of 2024
- Wayland HDR/Game color protocol will be finished before end of 2024
- Nvidia 555/560 will be out for a perfect no stutter Nvidia performance
- KDE/Gnome reaching stability and usability with NO FKN ADS
- VR being usable
- More Wine development and more Games being ported
- Better LibreOffice/Word compatibility
- Windows 10 coming to EOL
- Improved Linux simplicity and support
- Web-native apps (Including Msft Office and Adobe)
- .Net cross platform (in VSCode or Jetbrains Rider)
What else am I missing?
I may because I'm clearly an outlier and it's a bit of an experiment now, but...
... you realize how just saying that is an absolute dealbreaker for Linux, right?
I mean, if you're a base Windows user trying Linux for the first time, it is arcane gibberish. If you're just trying to get a working computer it's a major hassle. If you're, like me, a grumpy old fart, you're getting flashbacks of sitting in front of a Pentium-133 doing this exact exercise of flipping back and forth across environments and bumping against different frustrations on each and just can't believe this is still the feedback you're getting online this many decades later.
Yeah, honestly given the time this has been at play I'm surprised nobody has tried to do that type of full control integration besides Google. Given how well ChromeOS and especially Android worked as platforms why hasn't... I don't know, Valve? Adobe? Apple, even? tried to create a major desktop PC take on Linux that does have the type of support and sensible UX you want out of the box?
It's probably too late now that MS is hell-bent into turning Windows into that sort of platform, but there was a period of time there, probably during the Win8 debacle or the early parts of Win10 where you could have come up with a "big boy ChromeOS" take that would have gotten this done. It's nuts that Valve only got as far as doing the basics of SteamOS and then failed to deliver on their promises of wider support before the community basically turned installing that into the same kind of nightmare every other distro is.
Well, no, that's not applicable here. I'm suggesting a proprietary, corporate-backed desktop default in the way we have a proprietary, corporate-backed laptop reference in ChromeOS, a corporate-backed mobile reference in Android and a proprietary, corporate-backed handheld default in SteamOS.
It's not about covering everyone's use cases, it's about applying commercial priorities and funding to one specific use case.
I mean, you know the Linux community craves that opportunity, because the amount of hype around SteamOS when that dropped on the Deck was insane, and despite their clear lack of interest in expanding it into a Windows alternative for other product types there's been no pushback in those circles.
But how does that differ from Fedora or Ubuntu, besides popularity?
That's a fair point. I suppose conceptually that's what those organizations were trying to do. So it's a failure in execution which then probably acts as a deterrent for other corporations considering stepping up to challenge MS on modular desktop PCs, which aren't that big of a market in the first place.
I guess if you were going to do that you'd pair it to rigid hardware instead for that reason and at that point you're Apple and we're talking about MacOS.
Fedora is considering switching to Plasma by default.
https://www.phoronix.com/news/Fedora-Change-KDE-Default-Prop
Many big maintainers are working hard to make the experience better for the average user. Things are getting better.
As a person that also went "screw it, I'm going back to Windows 95" for the exact same reasons in a previous millenium...
...no they aren't.
This isn't new, this has been the way this works for decades. Sure, there have been improvements, but also plenty of steps backwards. This run at it has been a noticeably worse experience than, say, being told about Ubuntu and being surprised at it having a smooth installer for the first time. Sure, gaming then was a no-go, but with PC hardware being a much narrower path then, it was so much easier to get the hardware itself running.
And yes, it was about to be the year of Linux desktop then, too.
This is something people fail to realize, and I think part of it is because Linux people tend to surround themselves with other Linux people.
I have been helping my friend get into Linux, we picked a sensible distro, fedora, with the default gnome spin. He loves the UI, great.
But there is a random problem with his microphone, everything is garbled, I can't recreate it on my hardware and it's unclear.
He reads guides and randomly inputs terminal commands, things get borked, he re installs, cycle continues.
He tries a different distro, microphone works, but world of Warcraft is funky with lutris, so no go.
The result is, all of this shit just works on windows, and it just doesn't on Linux. Progress has been made in compatibility, but, for example, there was a whole day of learning just about x vs Wayland and not actually getting to use the computer. For someone who has never opened a terminal before, something as simple to you and I as adding a package repo is completely gibberish
Yes you can learn all of this, but to quote this friend who has been trying Linux for the past two weeks "I'm just gonna re install windows and go back to living my life after work"
When you have 20 years of understanding windows, you need to be nearly 1 to 1 with that platform to get people to switch.
It's not about being 1:1. I have used Android, iOS, MacOS and a bunch of other systems. Most of those have been easy to adapt. In fact, like your friend, I prefer the GNOME look because the MacOS-ish UI feels fun and fresh after being on Windows for so long.
It's the ratio of troubleshooting versus usage and the lack of definitive resolution for things.
FWIW, I just went back to Windows, not because I found the terminal commands hard to grasp (I started working with computers in the 80s, I'm not intimidated by a command line), but because they often didn't match what tutorials said, or because something that didn't work didn't generate an error and simply did nothing, or because something just randomly stopped working for no reason and just dangled there, broken, indefinitely.
Say what you will about how haphazardly Windows is architected, but most of the time if something breaks it's a matter of either installing the right thing, uninstalling the right thing, finding the right setting or reinstalling the OS. That sense of rebuilding your bike as you ride on it that Linux still forces upon you is just so friction-heavy, and the failstate of it is so frustrating. There's a reason why a dedicated Android or ChromeOS for your hardware feels just fine but desktop Linux is untenable for 90% of users, and it's not the 1:1 parity with Windows.