I've installed Mint 21.1 on a ond laptop for my son and it is really interesting. Recognised all the things inside, which W10 didn't and had to search for drivers and it lives another day, cause with Win10 it was hellishly slow. I was thinking dual-booting myself, keep Windows for work related stuff and Mint for relaxing. Can't for now cause I dont have enough space on primary drive and don't want to do it on different ones. But it sure impressed me the way it worked from the start.
Edit - it's my first dab in Linux so for me was a rather pleasant surprise after years of hearing about command pprompts and sudo this sudo that.... No normal people will do any command promt, ever.
Command prompt - in terms of day-to-day usage, I go to the command prompt in Linux about as often as I do Windows. One notable point that I need a command prompt in Linux for is when I install the drivers for my printer and scanner. Linux can often do it itself just like Windows can, but the auto install is often not a particularly good job of it, e.g. the auto installed print driver only has a small portion of the printer's capabilities.
Whether I have to type sudo or run an elevated command prompt in Windows, or manually install a driver in Windows (ie. through Device Manager), or do a registry tweak, it's all pretty similar IMO. If a "normal user" won't do that then they'll just call someone who will. I have many customers who are flummoxed at the prospect of installing a program in Windows.
I don't think there's an easy-to-establish "gold standard" of "no OS should demand this of its users" (e.g. command prompt usage), the only idea I can think of in this respect is that if some documentation is written for how to implement xyz on an OS, then it should basically always work unless there are some extremely unusual and serious underlying issues going on with the OS/hardware platform. I don't think it really matters if the instructions rely on the command prompt or device manager or whatever, as long as they work and the instructions are well-written, the only problematic point would be if there was a way to easily screw up when following the instructions and that screw-up has destructive consequences. For example I once accidentally deleted HKLM in a Windows registry. It didn't allow me to completely do it, just significant portions of HKLM
Instant OS reinstall.
I've flirted with *nix for over twenty years and have been using Linux full-time since 2018, and one thing that used to be the case was, for example I wanted to install a program: Fine, follow these instructions. The instructions didn't work, bizarre error message presented. Google error message, suggests abc is broken. Try to fix abc, hum, defg isn't right. And so forth. And that kind of problem typically happened early on in my attempt to test an OS, which for me was a showstopper.
Facebook
Twitter
Instagram