bionade24

Let's hope they'll use GNU Taler for this. I only heard it being considered in Switzerland.

If Linus would be a non-techie, he would have tried to install it with a graphical AppStore, it wouldn't have worked and he'd either given up or found the flatpak version of Steam, which would have worked. Not restricting power users is a good aspect. If I play around with Windows registry to force the removal of edge, Linus would blame me, not Windows. You have to differentiate between things normal users tried and things Linus attempted because he has some technical knowledge.

Some random user saying anything doesn't make anything true, you don't believe flat-earthers on the internet, either.

The bug was that you couldn't install steam without faking a the installation of a dep that went down the dependency chain ending in a conflict of essential packages. The functionality to still proceed is a feature. Linus could also just have copied rm -rf --no-preserve-root / from the internet as solution and would have trusted it blindly. If you want to be nannied all the way, I'd suggest you switch to iOS for everything.

IIRC it was already fixed when Linus did this, just not distributed. It was caused by the bluntness Linus developed due to unmeaningful Windows warnings in the 1st place.

Real people only use cat.

Eugen isn't the Fediverse. At least for the Twitter Exodus most Masto instances used a fork that allowed for longer posts than Eugen liked. There's 0 reason to care about what he's doing, he can't control the network.

And you still couldn't be sure, could be parsed the other way around for historic reasons.
Just reading the source code (if possible ofc) is imho easier than reading.

You still don't know which location is preffered and how get they get merged. In my experience, digging into the source is the most straighforward. But my usual problem is more that the config option doesn't do at all what the documentation says it does.

The *nix equivalent is the lsof command. This doesn't help you finding out in which hierarchy config files are parsed when the program accesses multiple ones, which is often the case.

What's imho worse is how often config options or command flags don't actually do at all what's described in the manpage. I then have to dig into the source code once again and since you have to read through the whole behaviour it takes much longer than just looking up where the program tries to read config files.

Please - if you find such wrong docs in Open source software, submit a fix to the doc. It's as important as normal bugfixes.