Hi, everybody Recently, a guy noticed that I was using it and asked why? For me it because in Linux many things are done through the terminal because Linux has many different desktop environments

He also compared terminal commands with cheat codes in GTA and other games, he understands what benefits you take from them, but not from terminal commands

  • BudgieMania
    arrow-up
    37
    arrow-down
    1
    ·
    10 months ago
    link
    fedilink

    because every additional layer of abstraction disrupts communication with the Machine Spirit even further

  • gerryflap
    arrow-up
    25
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    For tasks that I know, I’m faster in the terminal. For tasks where I’m less familiar or that are very important (like disk partitioning) I prefer a GUI because with a GUI I can usually see a bit better what I’m doing.

    Terminal tasks for me include copying stuff, setting folder permissions, uncompressing or compressing folders, quick edits in vim, etc.

  • Trent
    arrow-up
    24
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    Command line is a lot more powerful for a lot of cases. Most CLI programs are written with the idea that the caller might be another program, so they tend to be easy to chain with pipes and redirection. So you have tons of simple tools that you can combine however you need.

    • umbrella
      arrow-up
      1
      arrow-down
      0
      ·
      10 months ago
      link
      fedilink

      this and its sometimes faster than sifting though a gui

  • LainOfTheWiredEnglish
    arrow-up
    19
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink
    1. It feels great
    2. Terminal programs run on a potato
    3. They are almost always way more powerful then their GUI counterparts
    4. They integrate with scripts and other tools for unlimited power and flexibility!
    5. You feel like a hacker man
    6. Your IT literate friends think you are cool
    7. You can really do things your own way

    So yeah I love using the terminal for almost everything

    • theUnlikelyEnglish
      arrow-up
      1
      arrow-down
      0
      ·
      10 months ago
      link
      fedilink

      Can confirm #6. Wife calls it dark screen and does indeed think I’m cool for using it.

  • cetvrti_magi
    arrow-up
    18
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    Because I prefer using keyboard for almost everything and in most cases terminal is faster than GUI.

  • dreugeworst
    arrow-up
    13
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    Because you can’t (easily) program gui apps to automate tasks, but combining a few terminal programs to get more complex behaviour is really easy

  • lorty
    arrow-up
    13
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    Because every IDE implementa a different git interface and I can’t be bothered to figure out where they hid the commit, push, pull etc. buttons this time.

    • azimir
      arrow-up
      5
      arrow-down
      0
      ·
      10 months ago
      link
      fedilink

      When teaching programming classes it’s awful trying to figure out every IDE’s git interface that my students are using. Each IDE puts the buttons in very different layouts and they even change the names of the buttons because they don’t like the way git itself named operations. It’s untenable to know them all and actually be efficient and helpful as the instructor.

      Instead, I say they’re welcome to use the IDE, but the class materials use the canonical underlying command line tools and terminology. They just need to search for how to translate the real git interface to however their chosen tool does the same operation, but it’s up to them to figure it out.

      When they do ask for help, I bring up the terminal (usually even inside the IDE) and run the git commands just like we went over in class.

    • richieadlerEnglish
      arrow-up
      4
      arrow-down
      0
      ·
      10 months ago
      link
      fedilink

      Damn I hate with a passion the IDE interactions with source control software. I may make use of the visual information they give me, but I still execute the commands in the console.

      • c10l
        arrow-up
        3
        arrow-down
        0
        ·
        10 months ago
        link
        fedilink

        Same. Git GUIs can be great for examining commit trees, visualising patches, etc. For any write operations (this includes things like fecth and pull which write to .git), it’s all in the shell.

  • FractalsInfinite
    arrow-up
    12
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    Because Gui’s don’t show advanced options and so I know/understand exactly what is being done. (e.g. I would always use apt over mint’s package store so I could see what it did, how much time I had left, download multiple applications at once and see if the package made a random config file somewhere)

  • Dio9sys
    arrow-up
    11
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    I like using the terminal because of 3 main reasons:

    1. I like using my keyboard
    2. I like doing multiple things in one window
    3. Verbosity

    I’m pretty quick with typing, but sometimes I can’t see !y mouse at first, so it’s just faster for me to type out what I want to do as long as I know the right arguments for it.

    My average workflow at work as me doing frequent saml logins and going between multiple kinds of databases. It’s just easier for me to run the saml cli command and then run the SQL CLI command I need instead of messing with datagrip settings and stuff. Also I recreationally run some servers and it’s just easier to ssh into the server, make the changes I need in something like nano or the redis CLI tools and then log back out. This means I’m just plain more comfortable on the terminal in certain situations like config editing, writing posts for my gemini capsule, etc.

    Sometimes when I run a GUI program I’ll get big loud silence and don’t know what to do. In that case I genuinely enjoy using the terminal and running an equivalent command with verbosity settings so I can see what it’s doing or not and can track down any errors.

    On top of those reasons, I’ve been playing with RISC-V architecture lately and, while the xorg riscv64 port is admirable, I just get better performance rn by running my RISC stuff through tty.

    I recognize that not everybody is going to have the same use case and workflows as me, but I’m pretty comfortable with what I’ve got 😅

    • beeng
      arrow-up
      2
      arrow-down
      0
      ·
      10 months ago
      link
      fedilink
      • verbosity

      That mean you install powershell on linux?

      • Dio9sys
        arrow-up
        1
        arrow-down
        0
        ·
        10 months ago
        link
        fedilink

        No, I just run everything with -vvvvvvvvvv so I can see my computer yelling at me

        • beeng
          arrow-up
          1
          arrow-down
          0
          ·
          10 months ago
          link
          fedilink

          -vvvvvvvvv makes everything CAPS?

  • digdilem
    arrow-up
    11
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    Only one of the ~250 linux machines I maintain has a gui.

  • www-gem
    arrow-up
    11
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    Terminal is faster when you’re used to it and sometimes offer more customization options to some apps that has both a GUI and TUI/CLI version.

    I use the terminal (st with zsh and tmux) for:

    • file management (advcpmv, fd, trash-cli, fzf )
    • emails (neomutt)
    • text editing/coding (neovim)
    • project management (taskjuggler)
    • image viewing/organization (ucolla,ge)
    • online video browsing (ytfzf)
    • calendar (khal)
    • ssh
    • vpn
    • news aggregator (newsboat)
    • web, bookmarks manager (buku)
    • passwords manager (pass)
    • dotfiles manager (stow)
    • not in the terminal but I also have a lot of scripts used in rofi to control my audio input/outputs, launch a web search, access my bookmarks, autocomplete username and password fields

    I’m sure I’m missing some obvious tools I use daily. It’s hard remember everything when it becomes so natural.

    I have shared my experience with some of these tools here.

  • magic_lobster_party
    arrow-up
    10
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    The terminal is a power tool. I can do stuff with it that’s slow or inconvenient with graphical tools.

    I really like the piping capabilities of the Linux terminal. Incredibly useful for text processing.

  • Caveman
    arrow-up
    10
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    I run stuff in the terminal because it’s nicer than clicking. It’s like a shortcut-only way of interacting with the computer when you get into it.

    I make aliases and bash functions for everything I do often and is tedious to type / click like running steam games.

  • pixelscriptEnglish
    arrow-up
    10
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    Here’s the ELI5 answer I’d give to your friend:

    Computers are like servants. They do whatever you ask of them. But to be able to ask them things, you must do so in their language. On the extreme low level that means writing code to make programs, but on a higher level, it means talking to programs someone else already wrote using special commands.

    The buttons and switches on a GUI that you can click on with a mouse are like pre-recorded commands that instruct the computer to do some specific thing. The button or whatever will have a symbol or text description that lets you intuitively know what it’s for, and when you click on it, it plays a pre-recorded command to the computer in its language that tells it to do that thing. With these buttons, you can ask things of the computer in its language without having to know that language.

    As you get more intimate with the computer, this system can start to feel a bit stiff. You’ve essentially got a butler who doesn’t speak your language, and any time you need to give him a task, you have to fumble through a basket of pre-recorded tape recorder messages to find the one for the task at hand, and play it to him. For more complex tasks, you may need to chain several of these together. It gets slow and awkward. And god forbid you don’t even have a tape recording for the thing you need.

    It’s easier if you learn the butler’s language yourself. Then you can ask him for things directly. You’re not bound to any collection of pre-recorded messages to use, you can tell him exactly what you need. And if you don’t happen to know the word for something, you can look it up. It cuts out all the faffery with fumbling over a tape recorder looking for the messages you need to play.

    Using a terminal is roughly the computer equivalent of speaking to your butler in his native language. You’re not limited to only the buttons and features any particular program lets you have; you can make up exactly what you need on the spot. And you never have to bounce your hand between a mouse and keyboard to do it, you can keep your hands in one position at all times, which really adds up over time in both speed and comfort.

    Practicing this will also give you the side perk of better understanding how the computer actually works overall, and what it’s actually doing. This knowledge can come in super handy when diagnosing problems with the thing. When a GUI gives up, a terminal can keep digging.