This video is not monetized. This video covers our serious concerns regarding the data accuracy of Linus Media Group, including Linus Tech Tips, ShortCircuit...
Yeah, this irked me too. I get trying to be the average person (and Pop! was also bugged at the time), but I find it really hard to believe that the average person would approach linux and completely ignore serious warning messages.
I work in IT. Average people tend to fall into one of two categories when presented with big scary warning messages.
Category 1: They freak out and immediately ask for help, and tend to be very skeptical of anything you tell them to do until the message goes away.
Category 2: They ignore the message and YOLO it like Linus did, then call for help hours or days later when something inevitably breaks.
It’s rare for either group of people to read an comprehend the message in it’s entirety.
To be fair to the newcomers, most tech literature (messages, UI text, manpages, etc) is written by people who already know, for people who already know. It is meant as a reference for developers, not as an accessible documentation. So, for newcomers, the documentation, and accessible communication, is severely lacking at best, and non-existent at worst.
I some cases sure, but a lot of the time it’s simple stuff like “Save changes before quitting?” or “You need to restart to apply updates. Restart now?” and they still can’t figure it out.
In that case, there’s no reason to pretend to be the “average person” at all, and Linus may as well have just learned how to use a system before reviewing it.
Yeah, this irked me too. I get trying to be the average person (and Pop! was also bugged at the time), but I find it really hard to believe that the average person would approach linux and completely ignore serious warning messages.
I work in IT. Average people tend to fall into one of two categories when presented with big scary warning messages.
Category 1: They freak out and immediately ask for help, and tend to be very skeptical of anything you tell them to do until the message goes away.
Category 2: They ignore the message and YOLO it like Linus did, then call for help hours or days later when something inevitably breaks.
It’s rare for either group of people to read an comprehend the message in it’s entirety.
To be fair to the newcomers, most tech literature (messages, UI text, manpages, etc) is written by people who already know, for people who already know. It is meant as a reference for developers, not as an accessible documentation. So, for newcomers, the documentation, and accessible communication, is severely lacking at best, and non-existent at worst.
I some cases sure, but a lot of the time it’s simple stuff like “Save changes before quitting?” or “You need to restart to apply updates. Restart now?” and they still can’t figure it out.
Have you met people? They do this with Windows.
In that case, there’s no reason to pretend to be the “average person” at all, and Linus may as well have just learned how to use a system before reviewing it.