Command line on Linux: Pro or Con?


Recommended Posts

Saw a post or two in this thread that decried the terminal or command line on a *nix box as some horrible thing.

Actually, I have grown to really appreciate its advantages.

  • I can post a command or two in the forum, and the person that needs it can highlight with a mouse, and middle-click in an open terminal to get the exact command. You can't do that with a set of Windows instructions (or instructions using a Linux GUI, either).
  • Output of a command (for an error log or such) can be posted in a forum and searched
  • Posted statuses and such from above use up less much less bytes than the graphical equivalent while also often giving more information.

For example, to check partitioning information on a Linux box, I would ask someone to post the output of a

fdisk -l

command. They would be able to post the results, like so:

Disk /dev/sda: 146.8 GB, 146815733760 bytes
255 heads, 63 sectors/track, 17849 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot	  Start		 End	  Blocks   Id  System
/dev/sda1   *		   1		  13	   97656   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2			  13	   17850   143277083+   5  Extended
/dev/sda5			  13		 254	 1937499+  83  Linux
/dev/sda6			 254	   17850   141339583   83  Linux

which shows a good amount of detail, and you can even see that there is a problem because partition 1 (1-13) overlaps the extended partition 2 (13-17850).

Simple paste of one command, and copy/paste results that can be reviewed.

In Windows, to see partitioning (using the sample XP box I am supplied here at work), I would have to say:

  1. Click Start, "Settings", select control panel
  2. In the control panel, click Administrative Tools
  3. When you see your admin tools, click Computer Management, and the management tool will open
  4. In the left pane, find "Disk Management" and click it.

and those instructions will get you to something that looks like this:

post-36818-1226591304_thumb.png

While it looks nice, it does not show the type of detail that will find an issue of overlapping blocks like posted above. Larger image. Less informative.

Having a terminal to use isn't such a horrible thing, in my opinion. As long as there are also GUI tools for people to stumble through, if they needed to (in the case of the above example, gparted does quite nicely on Linux).

The best of both worlds, if you ask me.

Link to comment
https://www.neowin.net/forum/topic/696244-command-line-on-linux-pro-or-con/
Share on other sites

Don't have nothing against GUI's, but am all about the advantages of the command line too. A system that provides the combination of both is the way to go.

The terminal allows to do fast tasks without having to run a GUI program, wait for it to load and then execute that same task, that by now would have been done with a simple command.

How about bash scripting? There's so much you can do with a bash script made by yourself for a specific task. Same task could take ages to do in a program, such a file browser for instance.

command line is the best feature !

it allows you to create batch scripts that can be scheduled etc. And as you pointed out, you can get a lot more information than you can in a gui.

Unix got one thing right when they decided to build all the system tools in small efficient stand alone applications that can be linked to give out results that the authors might have never imagined. That can't be done with a gui

>Diskpart

DISKPART> select disk=0

Disk 0 is now the selected disk.

DISKPART> list partition

Partition ### Type Size Offset

------------- ---------------- ------- -------

Partition 1 Primary 298 GB 34 KB

or

DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info

---------- --- ----------- ----- ---------- ------- --------- --------

Volume 0 E DVD-ROM 0 B No Media

Volume 1 G 20061111_21 CDFS DVD-ROM 559 MB Healthy

Volume 2 F DVD-ROM 0 B No Media

Volume 3 D 320GB NTFS Partition 298 GB Healthy Pagefile

Volume 4 C Primary NTFS Partition 69 GB Healthy System

DISKPART>

I appreciate a good command line, I use Linux servers with CLI only and no GUI (Security)

But on Windows its possible to get to the innards with CLI, just need the know how

I appreciate a good command line, I use Linux servers with CLI only and no GUI (Security)

But on Windows its possible to get to the innards with CLI, just need the know how

on windows the CLI isn't as powerful as in unix, you can't pipe etc

also the tools provided by MS for the CLI are lacking, they improved with Msh (the MS shell....might be called something else now...) but last time I used it, it felt heavy (took a long time to start etc ) and that's not what a CLI is supposed to be

Imo -

Pro's: Can't disagree with anything already said. It's just so useful for complicated and mundane tasks.

Con's: It's a command line. If all you know about how to use a computer involves a point-and-click GUI, then a command line will stop you dead. A blinking cursor. It's in no way friendly and it doesn't give you any clues as to what to do next. There are no tooltips, and there are no buttons to click. I think it's a psychological thing. I think some people associate it with some kind of low-level access that, if you type the wrong thing, will render your computer completely inoperable. It requires knowledge of a language of abbreviated commands and, for file operations, a mental picture of the layout of the directory structure. None of which is required in a GUI, because it's simply drag-and-drop.

Those who know, know that it is good. Those who don't know view it with suspicion and disdain.

Command line is great for advanced and expert users, but say when average Joe gives Linux a try (which 99% of them won't do), but hypothetically let's say they install Ubuntu using Wubi. If they ever see the terminal, they will instantly start to freak out. The average Joe/Jane's need a GUI. Sure, some things maybe faster in command line, but you have to understand what you use is not suitable for others. This is why I hate Linux ###### who tell you to do everything in the terminal.

Command line is great for advanced and expert users, but say when average Joe gives Linux a try (which 99% of them won't do), but hypothetically let's say they install Ubuntu using Wubi. If they ever see the terminal, they will instantly start to freak out. The average Joe/Jane's need a GUI. Sure, some things maybe faster in command line, but you have to understand what you use is not suitable for others. This is why I hate Linux ###### who tell you to do everything in the terminal.

The truth is that 99% of Linux "######" DO use the terminal or command line for most/everything!

... This is why I hate Linux ###### who tell you to do everything in the terminal.

Wow.

It just seems that even a new user would prefer copy/paste of an instruction over a listing of steps on which app to select. What tab to select on that app, select "advanced", then a few options to set. There are times where a copy/paste command is quicker and more painless than firing up a GUI app.

And what is this about "everything"? I certainly said in my first post that having a GUI alternative is good for those who may be unfamiliar but want to muddle through menus and such themselves.

Surely, in the case of partition data that I used as an example, you could at least agree that it would be easier to paste that one line in a terminal (no typing even needed!) than to follow the steps to start up the app and get partition data to display.

If you still think that what I showed is quicker and easier for the GUI part than the cut and paste of the command... Then I will let you call me a "Linux ######".

EDIT: Weird, the plural "######" is not filtered. But the singular term "*******" is.

Command line is great for advanced and expert users, but say when average Joe gives Linux a try (which 99% of them won't do), but hypothetically let's say they install Ubuntu using Wubi. If they ever see the terminal, they will instantly start to freak out. The average Joe/Jane's need a GUI. Sure, some things maybe faster in command line, but you have to understand what you use is not suitable for others. This is why I hate Linux ###### who tell you to do everything in the terminal.

With you being tsu, tsu, tsupersonic! it would be expected that you would like to have things done as quickly as possible, tsupersonically i mean. Command line allows you to do just that. :)

although I've been lacklustre in learning the CLI, I'm steadily growing fond of its structure and how it lets the user operate.

I use to be scared of the CLI but this is changing. Nothing changes without my consent this is one of the advantages I think is a key pro in having CLI.

I like using the command line, its usually faster than a GUI based method.

but i mostly only use it for automated stuff, like batch files or scripts anyway, except on linux, i probably use the CLI more than the GUI on linux. I'm not particularly fond of the linux GUI's ive tried so far :p

i really wish you could do things like that in windows, thats another reason why i love osx. You get the best of both worlds.

true, i used to think just like that, but

i have linux boxes for everything i need linux for, and win desktop for browsing/casual gaming/watching videos etc. in result i don't have to buy overpriced mac hardware (yes, i know about hackintoshes, i'm too lazy for that) plus i can upgrade whatever components i need without problems plus i can run software the rest of the world does.

i could afford a mac, but -- i don't like the idea of sticking it up my ass when a new one comes out.

I like using the command line, its usually faster than a GUI based method.

I figured it was just my computer being slow, but yes I agree, it's much faster for me if I know what I'm doing. Major con though is that anyone new to Linux is going to be terrified at first if they've never used anything like it before. (I still worry about breaking things...so far so good though!)

Well, in Debian based systems, apt is a great way to download, install, or remove things. But also is Synaptic (GUI front-end). Other commands are great for CLI. It all depends what you want to use..... each to his own!

Weird, the plural "********" is not filtered. But the singular term "*******" is.

Now it is..... ;)

Definitely pro CLI. For many tasks it is much more effective than a GUI.

I can see why Joe User would be terrified by having to use a terminal window; for professional users like most of us here it shouldn't be a problem. If you can't figure something out - RTFM.

It's not just CLI, but all the programs you can use there, and the fact that everything on linux is a file and can be accessed as such. Even if you had a decent CLI on Windows it would be near useless as almost every Windows program is GUI only and info is stored in binary containers, so I understand why lots of Windows users don't realize the amount of stuff you can do with the CLI on linux/unix.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
    • Microsoft, totally not confusing /s 25H2 - Current for non-Arm based Windows 26H1 - Current for Arm based Windows 26H2 - Only for non Arm Windows
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!