Without fail, every Linux installation I had destroyed itself after a while.
Be it a full boot partition, some weird driver compatibility, etc, etc.
My Windows installations (granted, all work laptops) never destroyed themselves. Yes, some bugs here and there, but it worked well enough for home usage. You can't discount that.
... And then something happens and they want you to install Windows again.
As much as I like Linux, compared to Windows and Mac OS it's high maintenance. Once in a while, things will bork themselves. And you need to have at least a rough understanding of what's happening to fix it.
Also (and that's not a Linux problem per se) people seem to think if Windows breaks, MS or they themselves are at fault, if Linux breaks, that weird nerd and his hacker stuff are at fault.
What else am I missing?
The fact that 90% of people don't give a shit about ads, privacy or their operating system in general. They want a machine to open a browser, that's it. If Windows comes pre-installed, they'll use Windows.
The only realistic chance we've got is that MS shoots itself in the foot once more by all that Recall crap and businesses drop Windows. But that's a long shot.
It's actually astounding, how weirdly unmaintained Windows is in many areas. Just look at the settings chaos. There are three completely different settings trees, and at least for me, it's impossible to know which one to choose for a given task.
There's constantly stuff going on in the background for no reason and updates take forever and require 7 reboots. That's not okay.
Rather the wrong ones.
95% seem to be essentially professional box tickers. They don't care about security, but only about process compliance. As long as the scanner finds no CVEs, the app is secure.
I want people who actually know, how I can improve my code. I'm pretty sure I screwed up security stuff, but will never know.
I also promise, to pay you back, if you give me 10 million. No contractual obligations, but I totally promise!
Let that toilet bowl in.
It was never "trustless", but trust in the system as a whole.
The change you mentioned is more a change of the definition of "system", since now it's effectively an oligarchy.
Effectively they speed run something like 400 years of banking regulation and its history.
Because Ryan wrote it like this 10 years ago and nobody bothered to rewrite it in C.
Back then, I'd guess most developers were relatively fluent in assembly, so if there's only a small change to make, they'd just change the assembly and move on.
You don't swallow all of the milk and thus not all of the virus particles. There's always some residue that can then start to infect you just as if you inhaled the virus.
I'm not sure, if you're involved with the project, but if so: you really need to work on your communication.
You want hardware to last longer by providing software for it. That's it. Great goal, but you don't need half a bachelor's thesis for that, and you also don't need to tiptoe around the point.