• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Poll: GUI or CLI?

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Depends on what you're trying to do. Using a command-line strictly for the purpose of l33tn355 doesn't help me get my job done.
 
Originally posted by: Chaotic42

Well, for example when I look at something like Nero or Easy CD Creator, it just looks so cluttered and wasteful compared to a nice round of mkisofs and cdrecord.

I never really used a GUI until 1995.
Nero is not an example of a good GUI.

I use mkisofs and cdrecord almost exclusively (with Nero on occasion on Windows) but I would still characterize Nero as easier to use. I'd probably use a good CD writing GUI if it existed for Linux, but I was never fond of Xcdroast way back, and instead became familiar with the CLI tools.

The Nero GUI is definitely cluttered, but it easily wins as soon as you considering mastering a virtual ISO filesystem, done by a convenient drag & drop process.

With mkisofs, for more than a few virtual paths, you'll probably want to create a file listing the path mapping specs. You also have to remember to pass in the -graft-points option.
 
I mostly hate GUIs, but I acknowledge I'm more productive with them in many cases. On an average day, I'd say I'm about 50/50. Everything I do in a GUI I could certainly do on the CLI, but the time required to do so wouldn't be desirable.
 
gotta go cli - especially on my server. it's a whole lot easier to ssh into it from work than to set up a remote xw client.
 
Back
Top