thing with gui is you don’t need to memorize button locations and menus. If you do it’s poor layout. Good gui lets you find things you didn’t know you were looking for intuitively, without external resources or manual.
CLI requires you to know what exactly you are doing and is impossible to use without external resources.
Nothing against terminal but unless you know what you are doing and every command required to complete that action, it’s ass. If gui was so bad and cli was so good, guis would not be used by anyone.
I mean you dont go around copy pasting device ids and running commands for 20 minutes to connect your device through terminal when it is done with 2 clicks in the gui even by someone who has never used a pc before.
While you don’t need to memorize button locations and menus, the frustration is that it takes longer, and memorizing those details slightly mitigates. It’s torture helping someone do something while they hunt for the UI element they need to get to the next level of hierarchy. They will do it, in time, but it just feels like an eternity.
The main issue in GUI versus CLI is that GUI narrows the available options at a time. This is great, for special purpose usage. But if you have complex stuff to do, a CLI can provide more instant access to a huge chunk of capabilities, and provide a framework for connecting capabilities together as well as a starting point for making repeatable content, or for communicating in a forum how to fix something. Just run command “X” instead of a series of screenshots navigating to the bowels of a GUI to do some obscure thing.
Of course UI people have generally recognized the power and usefulness of text based input to drive actions and any vaguely powerful GUI has to have some “CLI-ness” to it.
Of course my terminals outnumber my browser tabs by about 3:1 right now. Commenting on an internet site needs neither scale nor complexity and a WebUI is fine for that.
thing with terminal is you don’t need to memorize commands, syntax and options. If you do it’s poor design. Good code lets you find things you didn’t know you were looking for intuitively, without external resources or manual.
Gui requires you to know what exactly you are doing and is impossible to use without external resources.
Nothing against gui but unless you know what you are doing and every click required to complete that action, it’s ass. If term was so bad and gui was so good, terminals would not be used by anyone.
I mean you dont go around copy pasting device ids and running buttons for 20 minutes to connect your device through gui when it is done with 2 commands in the term even by someone who has never used a pc before.
Your guide did literally nothing other than return errors. Seems like even you don’t know how to do this. And you follow wrong instructions that don’t work up with asking for coordinates of buttons for gui, this is scraping the bottom of the barrel. As in you’ve gone through the barrel, through the bottom, dug through the entire earth and are scraping the bottom of another barrel from under it.
I like the terminal on linux a lot, but with arguments like these you need to touch grass at least once a year my friend.
thing with gui is you don’t need to memorize button locations and menus. If you do it’s poor layout. Good gui lets you find things you didn’t know you were looking for intuitively, without external resources or manual. CLI requires you to know what exactly you are doing and is impossible to use without external resources. Nothing against terminal but unless you know what you are doing and every command required to complete that action, it’s ass. If gui was so bad and cli was so good, guis would not be used by anyone.
I mean you dont go around copy pasting device ids and running commands for 20 minutes to connect your device through terminal when it is done with 2 clicks in the gui even by someone who has never used a pc before.
While you don’t need to memorize button locations and menus, the frustration is that it takes longer, and memorizing those details slightly mitigates. It’s torture helping someone do something while they hunt for the UI element they need to get to the next level of hierarchy. They will do it, in time, but it just feels like an eternity.
The main issue in GUI versus CLI is that GUI narrows the available options at a time. This is great, for special purpose usage. But if you have complex stuff to do, a CLI can provide more instant access to a huge chunk of capabilities, and provide a framework for connecting capabilities together as well as a starting point for making repeatable content, or for communicating in a forum how to fix something. Just run command “X” instead of a series of screenshots navigating to the bowels of a GUI to do some obscure thing.
Of course UI people have generally recognized the power and usefulness of text based input to drive actions and any vaguely powerful GUI has to have some “CLI-ness” to it.
Sure terminal can be better in a few cases but the fact you are typing this from a guy browser on a gui os speaks for itself.
Of course my terminals outnumber my browser tabs by about 3:1 right now. Commenting on an internet site needs neither scale nor complexity and a WebUI is fine for that.
The alternative to memorization is the analog to “hunt and peck typing” where you just search the whole fucking screen/program.
thing with terminal is you don’t need to memorize commands, syntax and options. If you do it’s poor design. Good code lets you find things you didn’t know you were looking for intuitively, without external resources or manual. Gui requires you to know what exactly you are doing and is impossible to use without external resources. Nothing against gui but unless you know what you are doing and every click required to complete that action, it’s ass. If term was so bad and gui was so good, terminals would not be used by anyone.
I mean you dont go around copy pasting device ids and running buttons for 20 minutes to connect your device through gui when it is done with 2 commands in the term even by someone who has never used a pc before.
Ftfy buddy
Okay then how do I mount my drive through terminal and set it to automount every time and change it’s name to appear as “disk 3” everywhere?
man genfstab
genfstab whateveroptionsyouwant
Now give me all the X and Y coordinates of where i would click on my QHD screen for your example in gui plz
Your guide did literally nothing other than return errors. Seems like even you don’t know how to do this. And you follow wrong instructions that don’t work up with asking for coordinates of buttons for gui, this is scraping the bottom of the barrel. As in you’ve gone through the barrel, through the bottom, dug through the entire earth and are scraping the bottom of another barrel from under it.
I like the terminal on linux a lot, but with arguments like these you need to touch grass at least once a year my friend.
man genfstab gave an error? Neither CLI nor GUI is gonna help with simply not having something installed that the guide assumed.
Why would i install random software some rando on some random site tells me to to do a function my preinstalled gui(and terminal) can out of the box?
Yeah, you wouldn’t. My point is that’s because it’s preinstalled, not because of any GUI/CLI advantage.