The "sudo rm -rf" and equivilant horror stories get told all too often as mistakes even made by "skilled users" who were in a hurry, and while that particular problem is becoming less common there is still a minefield out there. Wider use case where we need IT support is worse since there are plenty of Microsoft and Mac favoring restrictions and lockdowns required in the name of corporate level security requirements and certifications add to the mess and "security concerns" you can't get corporate to move away from.
I'm a daily Linux user who has had to put years of a software developer career's time into learning the easier system administration aspects and working with those who handle the harder issues, but doing this in my career I have had to step back every time someone comes to me with a problem. Once I understand the problem then go on to ask "at a guess, how much time will diagnosing this even take?" with the estimates varying based on how standard the OS install or deployment is.
Time and a relatively small amount of training is the problem with switching users from Windows to Mac or the reverse. Switching to Linux is training and introducing a technical mindset into a person. Idiot-proofing the system is a major issue Linux hasn't solved yet. VDI systems and the like might be a step in the right direction, but as soon as your use case for Linux requires a "average user" to open a terminal the problems will pile up and the minefield is exposed.
Years removed from using a Mac I still think of it as the most "child-proofed" OS. Windows being less restrictive but still doing a good-enough job of locking up the more dangerous things while also not drawing attention to them on a regular basis. Linux is like seeing the dangers left out in the open with few useful warning signs beyond some generic unspecified danger signs around the worksite.