SpaceCadet

This isn't "Windows design"... this is just inherited stone age bullshit from the DOS days when the filesystem was FAT16 and all file names were uppercase 8.3.

NTFS is case sensitive in its underlying design, but was made case insensitive by default, yet case preserving, for reasons of backwards compatibility.

If Microsoft has to design something from scratch, without the need for backwards compatibility, they go for case sensitive themselves. For example: Azure Blob Storage has case sensitive file names.

a bash script to reinstall f—ing everything again

Why would you ever want to do that?

First of all, almost any Arch update induced problem can be solved by downgrading the offending package to the previous version, which handily is available in /var/cache/pacman/pkg/. This is an essential Arch troubleshooting skill.

Even an unbootable system (which has only happened once in my 10 years of using Arch because I didn't read important news) can be fixed this way, because you can always boot from the installation usb stick and then use arch-chroot to access your installation and fix problems.

Secondly, if the problem was indeed caused by an Arch update, you will just reinstall the problem if you run a reinstall script.

If your average Windows user calls tech support, they’ll get a simple answer

They'll get a simple answer alright. In fact, they'll be lucky if they get any answer at all that is not reboot, retry, reinstall or some other cargo cult nonsense from some on-paper "MCSA" in a third world country.

And sorry for going on a rant here, but Windows tech support forums are truly the shit tier of all tech support forums, because very few people actually have the skill to properly diagnose problems in Windows when something outside of the realm of expected behavior occurs. It's all learned behaviorisms instead of understanding: reinstall your drivers! defrag your hard drive! run ipconfig /renew! clean your cache folder! delete your cookies! Never: "look in the system eventlog for an error event coming from this source, and tell me what the error code says"

What is the problem with "jargon" anyway? You can't discuss technical things without using technical language.

If you take a bunch of Windows nerds (yes they exist), and get them talking about group policies and registry edits and powershell cmdlets, you get the same thing.

But people whose life or personality doesn’t revolve around their computer should also be protected from user hostile and privacy invading practices.

people not knowing shit about tech is not their fault

I don't agree with much else of what you are saying, but you are quite right here. We should indeed not throw people under the bus because they're not tech savvy and only know how to use Windows. They need to be defended from all those horrible anti-human and privacy invading practices by Microsoft and other Big Tech companies as well, and we should keep fighting and pushing back on those companies pushing their anti-human features, regardless of whether an alternative exists.

BUT, ultimately Linux is the answer, and people are not wrong for pointing that out. It's the only viable alternative that is user respecting by design. It's the only way to free yourself from the abusive relationship between you and Microsoft, because much like an abusive partner, Microsoft will never change. So if you're tech savvy, and you would be able to switch to Linux but for some reason you don't, I have little sympathy for your Windows problems.

Ah crap, was replying on an old tab that I hadn’t refreshed.

Ah crap, was replying on an old tab that I hadn't refreshed.

It was much easier to “hide” sit back then unless you were in the know in the industry.

It wasn't hidden. Everybody knew back in the day what an evil piece of shit he was.

It has just been forgotten about and many current adults weren't old enough, or even around, in the heyday of his evil empire, so he has been able to whitewash his image. My 50 year old ass remembers though. Fuck Bill Gates.