5,911 karma · joined June 4, 2019
They keep getting away with it, and nobody has any idea when the buck will finally stop.
Companies like Microsoft and Adobe have maintained a business software monoculture for decades. Nobody has invested significant resources into competing products, just tiny companies and open source volunteers putting out niche alternatives. Microsoft could probably double their prices, and double the built-in advertising, and most customers would complain loudly and keep using them. Docx files, PSDs, PDF forms, etc with any complexity will only ever run properly in one corresponding proprietary application.
Given the refinements to the hardware, the modern scale of manufacturing and accessible market, and the sheer amount of engineering manpower a tech company can bring to bear nowadays, you'd think standards would have risen into the stratosphere, but instead the tech consumer is cowed into accepting slow, buggy, abusive, invasive trash.
I do. It's not without its problems but currently it's the least bad solution.
Actually, where I was sitting on a decent PC with broadband Internet at the time, everything was much, much faster. I remember seeing a video on here where someone actually booted up a computer from the 2000's and showed how snappy everything was, including Visual Studio, but when I search YouTube for it, it ignores most of my keywords and returns a bunch of "how to speed up your computer" spam. And I can't find it in my bookmarks. Oh well.
Then you want something that directly copies Windows. Gnome doesn't do that; it very much does its own thing, which confuses regular people who typically just want an unenshittified Windows.
> 1. Security
Linux (and Unix before it) has always had security mechanisms built in. File permissions, setuid bits, namespaces. Any old program shouldn't be able to access /etc/passwd, and likewise the `<input type="password">` in my browser should be protected. Wayland's problem isn't that it tried to add security, but that the design and development process went horrifically wrong so that 17 years after the first release, people still have trouble with screen sharing.
> 2. Performance
The client-server model is obsolete and unsupported by modern applications (and nowadays there are easier ways to do remote GUI access) and keeping it was just a big pile of tech debt.
The problem wasn't that Wayland tried to fix things, it's that the process took 17 years and still isn't finished or particularly successful. My uneducated guess at why Wayland failed to succeed is that it went for extreme modularity and refused to say (back in like 2009) "Here's the security mechanism everyone has to use to take screenshots, etc. If this breaks your spacebar heater, sucks to be you." Rather than just define a single API where 99% of graphical applications and desktop utilities can do the sorts of things they already do on Windows and MacOS, and call it 1.0, instead they built a sprawling monument to bikeshedding and over-engineering.
1. Security - Any program using X11 can read keystrokes, passwords, or the contents of any other window. Fixing this would break all existing X11 applications.
2. Performance - X11's client-server model doesn't work with hardware accelerated graphics, requiring hacks to get around. X11 is basically stuck with this legacy.
The ground-up re-design of X11 to fix those two issues is Wayland.
Speaking of which, I recently bought a Ryzen Framework laptop assuming the recommended Linux distro would run smoothly, but unfortunately I hit a few glitches, including a really annoying amdgpu bug that keeps making the screen flicker. I might have to mess with kernel boot parameters. Disappointing.
Since the Steam Machine is meant as a consumer product, hopefully it will run Linux solidly, and that's a big plus for me. I wouldn't touch Windows with a 10 foot pole these days.