CLI is relatively consistent, UIs keep changing; documentation on how to do X will be outdated extremely quickly and unlike CLI those changes aren’t documented nor searchable
GUIs are straight up not documented, you can’t know an option exists unless you stumble on it
Even if the GUI is explicit enough to count as documentation, you can’t search a GUI; the CLI documention can be searched for keywords
You can’t automate GUIs if the need arises
I’m not against GUIs in general, but they should always be supplementary to CLI, otherwise you end up with windows
To do this setting, you have to open up regedit, and…
That part of Windows isn’t so pretty. A quick copy-paste of a CLI is so much better than opening up regedit. Powershell has improved this, but for a long time this was the approach for settings microsoft couldn’t be bothered to make intuitive UI for.
No, Windows as in “this setting is hidden under this menu, that submenu, here click to open another sub-window…”. This will happen any time a dev tries to arrange settings in logical way (instead of flat list of toggle and input boxes), because “logically belong together” and “actually often used together or one after another” are not the same, and also dev logic, internal system logic and user logic are also three different things. Result - mad maze
Which is why many tinkerers like CLI - at least one can run man something or something --help in most cases
I get what you meant, I was just making a little joke, though I feel like there’s a huge difference between shitty ui that can’t be bypassed and reasonable ui that still can’t be bypassed. The latter is usually managable and tolerable.
I personally prefer having both options but in general I go with a UI.
I feel like a dinosaur at work because many times I have no idea how to use the different programs there, mostly because everything is so incoherent (to me).
And I don’t mean a large living dinosaur cracking trees in two while chasing my dinner.
I mean a bunch of sad brown bones held up by sticks in a dusty museum everyone walks by.
Nah
I’m not against GUIs in general, but they should always be supplementary to CLI, otherwise you end up with windows
This guy operates systems.
Windows without the garbage? I’m okay with that.
To do this setting, you have to open up regedit, and…
That part of Windows isn’t so pretty. A quick copy-paste of a CLI is so much better than opening up regedit. Powershell has improved this, but for a long time this was the approach for settings microsoft couldn’t be bothered to make intuitive UI for.
No, Windows as in “this setting is hidden under this menu, that submenu, here click to open another sub-window…”. This will happen any time a dev tries to arrange settings in logical way (instead of flat list of toggle and input boxes), because “logically belong together” and “actually often used together or one after another” are not the same, and also dev logic, internal system logic and user logic are also three different things. Result - mad maze
Which is why many tinkerers like CLI - at least one can run
man somethingorsomething --helpin most casesYeah, man is clutch… I wonder if people would be so intimidated by CLI if everyone knew how easy it was to learn commands with man
A lot of people are afraid of text. Like, they see text on a screen and get visibly scared. Weirdest shit ever.
I get what you meant, I was just making a little joke, though I feel like there’s a huge difference between shitty ui that can’t be bypassed and reasonable ui that still can’t be bypassed. The latter is usually managable and tolerable.
I personally prefer having both options but in general I go with a UI.
I feel like a dinosaur at work because many times I have no idea how to use the different programs there, mostly because everything is so incoherent (to me).
And I don’t mean a large living dinosaur cracking trees in two while chasing my dinner.
I mean a bunch of sad brown bones held up by sticks in a dusty museum everyone walks by.