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

    • The proportion (or number of iterations) has nothing to with this aspect of Copyright I am describing. In short, it doesn't matter how many times the manager tells you to change something or how. Your work product is always YOURS until and unless you then assign that to the person representing the client/company, usually for financial compensation -- either in salary or as a subcontract work for hire payment. if iterations determined copyright, then businesses would have learned to just keep making changes until they could claim they owned the copyright, without having to compensate the artist for their work. And that would be BAD. The only place where the amount of changes does have a role is in how much does a human modify a previous public domain work (from any source) before it is considered fair use or their own work, etc. For example, if a human makes substantial changes to a public domain (re: AI, by definition) work, then they can then claim that derivative work as their own...but NEVER the original version, of course. That's why anyone can make a movie about Dracula, for example, as long as it is based on the public domain novel, but not if they take new ideas from copyrighted movies made afterwards. As one of the people who personally advised the US Copyright Office on their recent ruling on these very issues, be assured that I specifically used the terminology precisely -- though I made it simple enough for laymen to understand it. If I made this confusing by doing so, I apologize. But, to be clear regarding your assumption that I would agree to your second statement that I quoted above -- the answer is NO. If AI does the work, no matter how much "direction" you give it, it cannot be copyrighted. All AI generated content is in the Public Domain and therefore the copyright cannot be assigned to ANYONE, even you -- until and unless substantial modifications are made to it BY A HUMAN BEING (yourself or a contracted artist/writer/etc.) and then that copyright on the derivative work is legally (in writing) transferred to you. This is a critical distinction. And it is important that people, especially AI sloppers, understand this. For example, YouTube is not paying AI slop generators for the copyright, etc. of their AI slop. What YouTube is doing is sharing AD REVENUE for permission to publish your AI slop. Copyright/ownership/rights never come into it. Importantly, that means that anyone can copy any AI slopware on YouTube, etc. and rehost it anywhere they want, even back on YouTube, and there is nothing legal that YouTube can do about it with regards to copyright protections, ownership, DMCA, etc. Anyone is legally free to use any AI slopware in any way they want. When this ruling was pending, I warned Disney legal of all of this before they did their OpenAI deal -- that it would literally dilute their entire IP portfolio forever. They ignored that warning for the PR and stock bump. But that is why, when the ruling came down last year, Disney quickly extricated themselves from that OpenAI deal, even eating the initial upfront fees -- followed closely by OpenAI ending their entire AI video generating business model. They adjusted their PR release dates to make this less obvious to shareholders, of course. Phew. I hope that this clears up the key distinctions for you and anyone reading. If you have any additional questions or even hypotheticals about AI and Copyright, please feel free to ask.
    • Each of the devices displayed on this page now has a little volume meter next to it to show if there is audio actively playing. About time.
    • Owing to the nature of Windows feature enablement updates, it was distributed over Windows Update services as a complete system upgrade rather than as an ordinary cumulative update
    • Microsoft confirms Windows 11 26H2, urges IT admins to prepare for release by Usama Jawad Windows 11 typically follows an annual update cycle, but Microsoft recently broke that tradition a bit by releasing a "26H1" version in the first half of this year as a "scoped" build for select new silicon PCs only. This version was not available for customers using 24H2 and 25H2 builds, as Microsoft is busy preparing version 26H2 for them, confirmed officially for the first time. In a Windows IT Pro blog, Microsoft has urged IT admins to prepare for the upcoming release of Windows 11 version 26H2. The company has confirmed that this will be a small enablement package (eKB) that will simply light up certain disabled features that are already present in the operating system's code base. This means that the "refined" Windows update and deployment experience will be simpler and quicker, with minimal disruptions, as the feature update will simply toggle a few flags rather than performing a complete replacement. Microsoft has explained that this is all possible because the standard Windows 11 releases share the same servicing branch and hence, the same source code. However, this also means that Windows 11 26H1 users won't be able to upgrade to 26H2 as that is a different branch, but this is something we have known for a while now. Similar to previous annual feature updates, Windows 11 26H2 will offer the following support cycles: 24 months of support for Home, Pro, Pro EDU, and Pro for Workstations editions 36 months of support for Enterprise, Education, IoT Enterprise, and Enterprise Multi-session editions Microsoft has not confirmed a concrete release date for Windows 11 26H2, but noted that it is "coming soon". If we go by the ongoing release cadence, we can expect it to begin rolling out in early October 2026. As such, IT admins have been encouraged to begin validating Windows Insider releases in the Experimental Channel, plan rollout rings, and strategize the utilization of their existing deployment tools.
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      576
    2. 2
      +Edouard
      188
    3. 3
      Michael Scrip
      79
    4. 4
      PsYcHoKiLLa
      77
    5. 5
      neufuse
      72
  • Tell a friend

    Love Neowin? Tell a friend!