I'm trying really hard to come up with a scenario where optimizing the desktop experience for the average user is a bad thing.
For example, what keeps me on Windows (and WSL2) at the moment is that the freesync/variable refresh rate technology doesn't always behave as you would expect it to be, resulting in games that stutter, frame dip and eat inputs. Gnome devs have a branch pending final tests for vrr for months. KDE on Wayland is the best for what I'm asking atm but even that has its problems during gameplay.
And let's not forget the pains Nvidia's drivers cause compared to AMD on Linux for desktop. I built my desktop using AMD GPU and CPU specifically for Linux to play nice, and yet it doesn't for the only 2 games I play during my downtime. It's just sad.
Again, maybe I'm a sore loser, but it definitely feels like a lot of software is becoming increasingly hostile to me, personally because it's being optimized for a presumed average user. I have no beef with this average user and it's globally a totally correct optimization to make stuff work for them as well as possible, but it means that software makes tradeoffs that are inconvenient for me personally.
The most common use case is streamlined by removing options that clutter up the settings menu or banishing the buttons I press a lot into some tertiary menu, or niche features I rely on become unsupported and then get removed (of course with forced auto-updates, because the average user experience is improved by them) to free up developer bandwidth for the core features. And then I end up using a different off-brand window manager with the serial numbers filed off that barely works in general, but works for my specific 'workflow" exactly like I want it.
Of course, at the same time I also benefit from general improvements targeting the average user. It's only about the tradeoffs.
It's a bad thing if you're not an average user, because software aimed at the "average user" tends to be a pain in the butt for the non-average user. I would point to Windows, the entire web browser space, etc., as examples of this.
And it's not just about the average user. It's also about the compromises needed to make a product suitable for mass production. I already see the effects of that on Linux, in the form of things like systemd, snaps, flatpack, etc.
"Windowsification" is a admittedly vague concept, but tends to cover software that is gratuitously different, not a team player in the bazaar, prone to making land grabs through "embrace and extend", and reluctant to offer configuration options that conflict with its "opinionated" stances.
As an aside, I'm really sick of the systemd / "random pile of shell scripts" false dichotomy. It's trivial to turn a python script into a system service with runit, too. Simple, stable, and focused.
But lutris as it stands now breaks everything almost every time I use it. I had steam unlaunchable for over a week because of something lutris was doing implicitly. Now running steam directly off the CLI seems to be working for 90% of the games I play (which isn't a very long list).
Only thing I doubt I will be able to figure out is stuff like fortnite or anything that uses easy-anti-cheat (since their devs give a fuck about linux and effectively believe we are all hackers trying to ruin their game).
That's all I got, don't bother with Lutris unless you have an insane amount of time to debug which component is missing.
All the UX work is being done in the steam client itself and is not exclusive to the Steam Deck. In fact, the SteamOS ui is now available 1:1 in the good old PC Steam client, replacing the old Big Picture mode.
The only thing that doesn’t comes directly with Steam is Gamescope (but you can install it yourself easily).
Other than that, the SteamOS is just an Arch Linux with Steam installed, KDE and a Steam wallpaper.
https://steamcommunity.com/groups/SteamClientBeta/discussion...