Windows constantly says “this could harm your computer.” Just about any time you install software it does.
Remember when Linus Sebastian blew up Pop!_OS? As a Windows user, “This is likely to break your computer, do not do this unless you absolutely know what you’re doing. To proceed, type “Yes, do as I say.”” is something to walk right past.
I’ve done big forensic write-ups of it in the past and mapped it to the FAA’s accident chain model. It just so happened that he was using a distro with a weird forked DE (Pop!_OS) and just so happened that the version of the Steam package in the apt cache from when the install image was made was bugged in such a way that it would uninstall Xorg, and it just so happened that Pop!_OS didn’t run an apt update when launching their GUI app manager.
When Linus saw “failed to install Steam” he turned the petulant child up to 11 and started bitching about how you always have to use the terminal in Linux, and instead of googling the error message to find out “do an update and try again” he found a page that told him how to sudo apt install steam. Most instructions like that tell you do to an apt update before an apt install, so I don’t know if he either aggressively skimmed, deliberately ignored the update command because he’s used to how painful Windows updates are, or if he found a source that didn’t include it.
APT spat out a lot of stdout about all the packages it was going to remove, with a highlighted plaintext warning at the end which he failed to read or failed to heed.
Linus’ bad attitude was a major contributing factor to the incident.
Windows constantly says “this could harm your computer.” Just about any time you install software it does.
Remember when Linus Sebastian blew up Pop!_OS? As a Windows user, “This is likely to break your computer, do not do this unless you absolutely know what you’re doing. To proceed, type “Yes, do as I say.”” is something to walk right past.
Damn so thats why he ignored the warning… I never understood how he could write Yes, do as I say! by ignoring the obvious warning.
It seemed like he intentionally brick the system just to complain linux is bad
I’ve done big forensic write-ups of it in the past and mapped it to the FAA’s accident chain model. It just so happened that he was using a distro with a weird forked DE (Pop!_OS) and just so happened that the version of the Steam package in the apt cache from when the install image was made was bugged in such a way that it would uninstall Xorg, and it just so happened that Pop!_OS didn’t run an apt update when launching their GUI app manager.
When Linus saw “failed to install Steam” he turned the petulant child up to 11 and started bitching about how you always have to use the terminal in Linux, and instead of googling the error message to find out “do an update and try again” he found a page that told him how to sudo apt install steam. Most instructions like that tell you do to an apt update before an apt install, so I don’t know if he either aggressively skimmed, deliberately ignored the update command because he’s used to how painful Windows updates are, or if he found a source that didn’t include it.
APT spat out a lot of stdout about all the packages it was going to remove, with a highlighted plaintext warning at the end which he failed to read or failed to heed.
Linus’ bad attitude was a major contributing factor to the incident.
I too wrote something similiar here https://lemmy.dbzer0.com/comment/9956561
But didn’t expect it was Windows mentality to ignore all hazardous warnings
I think it played a part.