Linux

6540 readers

507 users here now

A community for everything relating to the GNU/Linux operating system

Also check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

399

Linux or Landfill? End of Windows 10 Leaves PC Charities with Tough Choice (www.tomshardware.com)

submitted 4 days ago* (last edited 4 days ago) by throws_lemy@lemmy.nz to c/linux@programming.dev

113 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] FizzyOrange@programming.dev 3 points 2 days ago (1 children)

The GUI option is only superior if it allows the user to skip the “Search for it” step.

Well yeah, and it usually does so it is usually superior. Did you have to Google how to connect to a WiFi network with a GUI? Of course not.

[–] Rivalarrival@lemmy.today 2 points 1 day ago

True.

Of course, I normally use a GUI on Linux to control WiFi, so that's not a particularly good example.

I regularly use shell scripts. I do know how to use the GUI to change file permissions to make them executable. But why would I open a file manager, browse to the file location, right click, select properties, select permissions, and save, instead of just firing off "chmod a+x *.sh"?

The last shell script I made for work automatically concatenated a bunch of PDF documents, applied a watermark, and printed two copies, all using command line utilities. A simple task that would take several minutes for the user to perform with GUI tools.

This was a simple task that was regularly performed by several users. The command line gave the user a simple, consistent method to automate this task. To my way of thinking, that makes the command line more user-friendly: it does not limit the user to the pre-configured operations allowed by the GUI.