After mulling over it for close to 14 years, it seems Microsoft is finally ready to kill off the Windows Control Panel soon. An official confirmation has been posted on its website.
I can’t argue with that, but I still take exception to the idea that only advanced users should be willing/able/unafraid to use the CLI. (not that I’m suggesting that you personally are pushing that viewpoint)
When you click a button, you have to read and interpret the label on that button, then hope the person who programmed it actually did program it to do what it is labeled to suggest, and sometimes even well meaning devs make this ambiguous. Plus, you have to FIND the button, which is kinda the subject of many of the discussions here in this very thread.
You go learn what ls does one time, and now you know how to list the contents of a directory. Spend two minutes each learning ps aux and grep, and now you know how to find process info for firefox (or whatever), plus you don’t need to know more than the very most basic things about grep to use it to search a text or conf file for a particular string. Or learn the ffmpeg command that you use most often for recursively processing a directory full of video files, and now you don’t spend 20 minutes mucking around with handbrake or whatever when prepping files to toss onto your Kodi box (I’m just pulling that one out of my butt). Hell, yt-dlp for downloading videos from just about anywhere is better than any gui tool I ever used.
I think it’s totally valid for people to prefer a gui, but I find it a little foolish that so many people just seem to intentionally shut off their brain when presented with a CLI - it’s different than clicking buttons, and it’s not always superior, but it should absolutely not be the bogeyman that many treat it as. You can probably learn less than ten commands to just a minimal level of proficiency and get a LOT done.
I can’t argue with that, but I still take exception to the idea that only advanced users should be willing/able/unafraid to use the CLI. (not that I’m suggesting that you personally are pushing that viewpoint)
When you click a button, you have to read and interpret the label on that button, then hope the person who programmed it actually did program it to do what it is labeled to suggest, and sometimes even well meaning devs make this ambiguous. Plus, you have to FIND the button, which is kinda the subject of many of the discussions here in this very thread.
You go learn what ls does one time, and now you know how to list the contents of a directory. Spend two minutes each learning ps aux and grep, and now you know how to find process info for firefox (or whatever), plus you don’t need to know more than the very most basic things about grep to use it to search a text or conf file for a particular string. Or learn the ffmpeg command that you use most often for recursively processing a directory full of video files, and now you don’t spend 20 minutes mucking around with handbrake or whatever when prepping files to toss onto your Kodi box (I’m just pulling that one out of my butt). Hell, yt-dlp for downloading videos from just about anywhere is better than any gui tool I ever used.
I think it’s totally valid for people to prefer a gui, but I find it a little foolish that so many people just seem to intentionally shut off their brain when presented with a CLI - it’s different than clicking buttons, and it’s not always superior, but it should absolutely not be the bogeyman that many treat it as. You can probably learn less than ten commands to just a minimal level of proficiency and get a LOT done.