• @[email protected]
    link
    fedilink
    39
    edit-2
    3 months ago

    I use Linux and I prefer GUIs. I’m the kind of person that would rather open a filemanager as superuser and drag and drop system files than type commands and addresses. I hope you hax0rs won’t forget that we mere mortals exist too and you’ll make GUIs for us 🙏🙏🙏

    • @[email protected]
      link
      fedilink
      7
      edit-2
      3 months ago

      I tried to learn superfile thinking it could make terminal more exciting but nah.

      Gimme that comfy file explorer gui.

      Totally agree.

    • @[email protected]
      link
      fedilink
      2
      edit-2
      3 months ago

      I would say “why not, to each their own” if not the thought about what else the filemanager is going to do with root access (like downloading data from web for file preview). But the general sentiment still stands, it is absurd to think that computer must be used only in one way by all people

    • @[email protected]
      link
      fedilink
      33 months ago

      FWIW I do use the file browser too when I’m looking for a file with a useful preview, e.g. images.

      When I do have to handle a large amount of files though (e.g. more than a dozen) and so something “to them”, rather than just move them around, then the CLI becomes very powerful.

      It’s not because one uses the CLI that one never used a file browser.

      • @[email protected]
        link
        fedilink
        33 months ago

        Yeah, when I need to inspect lots of images I just open the folder in gwenview.

        For peeking at a single picture or two through you can hold down control and click/hover on the filename when using Konsole. Love that feature. You can even listen to .wav files this way.

      • @[email protected]
        link
        fedilink
        13 months ago

        I once did rm \* accidentally lol. I now have a program that just moves files to trash aliased as “rm” just in case. I just don’t feel confident moving files in CLI

    • @[email protected]
      link
      fedilink
      English
      113 months ago

      I use both, depends a bit on the task at hand. Generally simple tasks GUI and complex ones CLI. Especially if I want anything automated.

    • Lv_InSaNe_vL
      link
      fedilink
      163 months ago

      Tbf, the file explorer is actually one really good argument for GUIs over terminals. Same with editing text. Its either simple enough to use Nano or I need a proper text editor. I don’t mess around with vim or anything like that that.

      Its all tools. Some things are easier in a file manager, some things are easier in a GUI.

      • @[email protected]
        link
        fedilink
        83 months ago

        I think it depends, if I have a simple file structure and know where stuff is, it’s pretty efficient to do operations in the terminal.

        If I have a billion files to go through a file manager might be easier.

      • @[email protected]
        link
        fedilink
        5
        edit-2
        3 months ago

        Yeah I prefer fancy text editor too. And my biggest heartbreak was learning that I can’t just sudo kate (there’s a way to use Kate to edit with higher privileges but I never remember how, edit: apparently it’s opensuse specific problem).

        Born to Kate, forced to nano

        • Illecors
          link
          fedilink
          English
          23 months ago

          The problem is running GUI code as root as it’s never been vetted for that. What you want, effectively, is to have EDITOR variable of your session set to kate and open system files using sudoedit. I’m a terminal guy myself, so this exact thing is enough for me. Having said that - I’m sure someone will chime in with a plugin/addon/extension/etc that adds this to the right click context for what I assume is KDE. Or you can try looking for that om your favourite search engine.

  • @[email protected]
    link
    fedilink
    13
    edit-2
    3 months ago

    On CLI I figure out the command I need once.

    Put it in a script.

    Cron it if I want it to be daemonized.

    Never think about it ever again.

    Anti-CLI folks just have a bad workflow.

    They see the script as the end, when in reality it’s a foundation. I rarely look at my foundation. I build on it.

    With this workflow I have dozens, hundreds, or thousand of automatic actions that “just work”. Idk, works for me.

    That said, if you prefer to click yourself to RSI to accomplish the same task, who am I to judge. I just watch and nod until I’m asked for a suggestion.

    • @[email protected]
      link
      fedilink
      23 months ago

      Yes 100%. I used to search the same problems over and over again until I started doing this. Plus this way you can also version them with git and deploy them to other devices.

    • @[email protected]
      link
      fedilink
      English
      53 months ago

      i imagine a perfect world in which everything has guis and the guis contain all the information I could want about what it does including the relevant terminal commands. In this way, the gui is also the manual.

      • @[email protected]
        link
        fedilink
        English
        43 months ago

        People complain KDE has too many settings and option while they are so much less that few cli programs combined. Imagine how cluttered that UI has to be

  • Psychadelligoat
    link
    fedilink
    English
    313 months ago

    Lol, meme’s backwards

    CLI evangelists try to shit on GUI constantly, as though it makes them better at computers. It doesn’t, kids

    Can see it in this very thread

    • @[email protected]
      link
      fedilink
      English
      83 months ago

      Was gonna say, never had anyone tell me to use a GUI over CLI

      but definitely had the other way around

    • @[email protected]OP
      link
      fedilink
      13 months ago

      Lol no. Many posts in this community recently making fun of gimp. Do you see anyone in the comments going WELL ACTUALLY IF YOU JUST USE IMAGEMAGICK? No. Plenty of things to complain about in the big DE’s like KDE and Gnome. But do you see people saying “just use tty”? Also no. Meanwhile you mention terminal once and you get at least two randos going on about how ThIs Is WhY LiNuX IsNt ReAdY. The meme is not backwards, your perception of reality is.

      • Psychadelligoat
        link
        fedilink
        English
        13 months ago

        Many posts in this community recently making fun of gimp. Do you see anyone in the comments going WELL ACTUALLY IF YOU JUST USE IMAGEMAGICK? No.

        You really don’t see why people would suggest using other GUI alternatives for image manipulation? image manipulation?

        Plenty of things to complain about in the big DE’s like KDE and Gnome. But do you see people saying “just use tty”? Also no

        “People don’t recommend entirely dropping GUI over one or two GUI issues!” Shocker, wow. They do condescendingly say 'just go into terminal and do x,y,z" though, like I said

      • Psychadelligoat
        link
        fedilink
        English
        43 months ago

        Nope, I encourage people to learn CLI but to also use GUI if it does what they need it to. The insult was only to people who think they’re superior for using CLI cuz that’s a silly stance

        Just laughing at the meme being backwards from my own personal experience

  • @[email protected]
    link
    fedilink
    English
    713 months ago

    That’s it, I need to hook up a controller to my PC so I can open Htop with a button press

      • Badabinski
        link
        fedilink
        143 months ago

        I genuinely use vim inside of termux on a daily basis. I dunno if I’m sick in the head or what, but I kinda like vim on my phone.

        • @[email protected]
          link
          fedilink
          English
          13 months ago

          What keyboard do you use? Do you need something like Unexpected Keyboard, or are you still able to be productive in vim with a more “standard” Android keyboard?

          • Badabinski
            link
            fedilink
            13 months ago

            Just default Gboard. It’s not pleasant, but it’s good enough for most of what I do.

        • @[email protected]OP
          link
          fedilink
          83 months ago

          Yeah I was gonna say that while it sounds completely unusable, it’s surprisingly not too bad actually. Some of the more complex shortcuts can get pretty tedious, but nothing that a good config can’t solve.

          I remember once my friend’s laptop died, and while it was in RMA he was using his phone with an external keyboard and mouse to develop a webapp lol. Just goes to show that any computing device that can run a web browser and VIM covers 90% of your daily software needs haha.

    • skulblaka
      link
      fedilink
      63 months ago

      Personally I just run gotop at startup and keep it on my second monitor. I know it’s a small waste of resources but I enjoy watching the blinkenlights.

  • @[email protected]
    link
    fedilink
    English
    43 months ago

    I worked customer support for a WordPress hosting company for a while, and about 70% of all of their troubleshooting was done in terminal. I never used terminal until that job. To this day I do most of my management the same way

  • RejZoR
    link
    fedilink
    English
    153 months ago

    There is nothing productive about searching online for some stupid command that is outdated for 2 years, breaks some shit and then you need another 2 hours to unfuck it because it’s not obvious from the long noodle of a command how to revert it. For something that could just be 3 clicks through control panel that every idiot could navigate without having to use online search engine.

    • gonzo-rand19
      link
      fedilink
      83 months ago

      Why are you entering commands that you read about online without knowing what they do? There’s a running joke that you need to enter rm -fr / to remove the French language from your system; it actually wipes the entire disk mounted to /.

      When you know what the commands do, using the terminal is always going to be faster (i.e., more productive) and use fewer system resources than using a GUI. That’s just a fact, sorry if it annoys you when people point it out. Whenever I need to move a lot of stuff around, I will always use mv instead of Thunar (my file manager) even though I prefer a GUI for most tasks.

    • @[email protected]
      link
      fedilink
      English
      33 months ago

      Go to a free online AI (or run one locally) and ask it your Linux questions.

      That way you won’t have to dig around old forums for answers.

    • Natanox
      link
      fedilink
      English
      53 months ago

      There are two different “efficiency” and “simplicity” perspectives clashing here. If you already are proficient with the CLI it’s arguably more efficient and/or simple than GUI solutions. If you are not then there’s literally a steep learning cliff in front of you, something many in the first group apparently either forget or otherwise want to ignore. It just sucks, some people in the community do have a lot of knowledge but a complete lack of understanding for people outside of their tech bubble.

    • @[email protected]
      link
      fedilink
      5
      edit-2
      3 months ago

      So, I wonder what happens if we add an option for every single one of those tasks in the UI? O right!

      msvc.exe is calling!

    • @[email protected]
      link
      fedilink
      73 months ago

      I agree. For regular user facing tasks, the terminal should be a last resort. I say this as someone who will happily defer to the terminal if I need more advanced control. But when basic configuration is subject to just CLI, it’s not as accessible as it could or should be

      • RejZoR
        link
        fedilink
        English
        53 months ago

        It’s not the own you think it is…

  • @[email protected]
    link
    fedilink
    273 months ago

    It’s is not either or. Also good cli require an eye for design just like gui. Lots of cli suck because there is no eye.

    • @[email protected]OP
      link
      fedilink
      43 months ago

      Yeah I totally agree. But still, I feel like there are much more terrible GUI programs out there than terrible CLI programs. The only truly awful CLIs I can think of is that tool for managing MegaRAID controllers that has the weird abbreviations everywhere, and shell interfaces to GUI-first bloatware like Dconf that were probably added as an afterthought. I think with CLI there’s only so many things that the developer can fuck up. It’s all just text. Meanwhile with GUI there are endless opportunities for truly horrid design. Think of Teams. Think of the github web interface. Think of the r*ddit redesign. Or go watch that Tantacrul video on Sibelius. CLI could never have such a breadth of terribleness.

      • xigoi
        link
        fedilink
        English
        43 months ago

        The good thing about CLIs is that if they suck too much, you can easily create a wrapper around them.

        • Badabinski
          link
          fedilink
          43 months ago

          Manpages are great though? They’re not the best if you need examples, but as a reference for the behavior of flags? I love’em.

            • Badabinski
              link
              fedilink
              23 months ago

              Eh, I’m fine with man pages. I looked at tldr before, but I’ve been using the command line for many things almost exclusively for like 10+ years now. I usually just need the reference details.

              • @[email protected]
                link
                fedilink
                English
                2
                edit-2
                3 months ago

                But that’s why I love tldr!

                It gives written examples of a handful of the most common use cases with a super brief explanation. It’s perfect for quick reference.

                But you do you, I don’t own any tldr stock or anything.

      • Ephera
        link
        fedilink
        English
        53 months ago

        Arch’s package manager is pretty terrible.

        Here’s two commands. See if you can guess what they might do:

        pacman -S package_name
        pacman -Syu
        
        Solution

        The first command installs a package.
        The second command updates all packages.

        I believe, there’s some sort of logic to the letters, but man, most users seriously do not care. They just want to install, update and remove packages 99% of the time, so they shouldn’t need to learn that intricate logic for three commands.
        I guess, you could use pkcon to do that instead, but that doesn’t really help new users…

        • @[email protected]M
          link
          fedilink
          6
          edit-2
          3 months ago

          Arch presumes that the user has some familiarity with CLI tools and can read documentation. You couldn’t even install it without using the terminal until archinstall became a thing. If it’s an issue, Arch is the wrong OS for you.

          Besides:

          • pacman -S - synchronises packages between the remote and local repo.
          • pacman -Q - queries the local repo.
          • pacman -R - removes packages.
          • pacman -F - queries the files of a package.

          Et cetera.

          • Ephera
            link
            fedilink
            English
            43 months ago

            I figured, I’d ruffle some feathers by saying that. 😅
            But yeah, I stand by my point. Just because your target users are capable of dealing with complexity, doesn’t mean you should be making use of that rather than simplifying usability, since your users have plenty other things they could be learning instead.

            I will caveat that I can see it becoming worth it to learn an intricate logic for a power user, when things fall into place and make sense at a higher level as you learn more about it.
            But in my experience, that’s just not the case with package managers. You need a few specific commands to be obvious and then the special cases can be obscure flags.

        • @[email protected]
          link
          fedilink
          English
          13 months ago

          AFAIK, arch never pretended to cater to new linux/cli users, I’ve always read it as a recommandation for advanced (or at least comfortable with reading docs and using CLI) users.
          My first time using arch required me following the arch wiki for install and when I finally got a working system (I’m as bad at following tutorials as I am at following cooking recipes) the pacman commands were not something I struggled with.
          But yeah coming from Debian where I had the gloriously intuitive apt syntax, I get your point.

        • Count Regal Inkwell
          link
          fedilink
          2
          edit-2
          3 months ago

          I only learned what pacman -Syu meant, after literal years of typing it in not knowing anything other than “this updates the packages”, because I got curious and googled it.

          To me it was just an adeptus mechanicus incantation.

          EDIT: And I still have no clue how ‘y’ translates to ‘refresh the database’. Like. Sure. S to synchronise from the server to the computer. And u to mark for update all the updatable packages. But – Why the fuck is ‘y’ the refresh?

          • @[email protected]M
            link
            fedilink
            3
            edit-2
            3 months ago

            The y stands for “yoink the database”.

            /s

            I think they either just ran out of letters, or y was seen as reinforcing the action (as in “yes, download the database too”), with yy being an even stronger action (“yes, download the database even if there’s nothing to update”).

        • @[email protected]
          link
          fedilink
          3
          edit-2
          3 months ago

          You think that’s bad? For as much as I love seeing a well-configured Nix system, it’s beginner-unfriendly learning curve is almost as bad as “compile everything yourself” distros.

          As a beginner, do you have a question about Nix? RTFM. You did? Well, wrong Nix. You wanted to learn something about Nix the language, but those docs were about Nix the OS and Nix the package manager.

          You just read a guide for using the nix command and wanted to install a program with nix-env? That’s an outdated guide. You should be using flakes and nix profile. You tried that, but it said the nix command is experimental so you didn’t do it? No, you were supposed to edit /etc/nix/nix.conf to enable them first.

          Don’t get me wrong here though, I like Nix. It just desperately needs an actual beginner-friendly beginner guide for flakes and nix command commands that doesn’t assume everyone is a software developer. 80% of the Nix documentation tutorials aren’t even relevant to regular users, only package maintainers and NixOS users.

  • Nabuu
    link
    fedilink
    353 months ago

    I mean, the reverse is also true, people have memorized which buttons, menus, etc they need to click/drag with do be productive. Sometimes i m OK with all the clicking, but most times I just want to do the thing now.

    Type 3 words or click through 9 context menus. 😅

    • @[email protected]OP
      link
      fedilink
      173 months ago

      Yeah exactly ANY interface made by humans speaks a design language, and it’s only “intuitive” insofar as the user understands that language. There’s nothing inherently “intuitive” about GUI, it’s a language that you’ve learned through a long process of trial and error. This is painfully obvious to anyone who’s ever had to help Grandma reset her gmail password out over the phone. Same for CLI. At first you’re copy-pasting commands from tutorials and struggling with man pages, but after a while you get used to the conventions. You learn that -h helps you out and --verbose tells you more and so forth. You could make the case that the GUI design language is more intuitive because it’s based of physical objects like buttons and sliders that many people are familiar with, but honestly ever since we abandoned skeumorphic design that argument rings a little hollow.

      • @[email protected]
        link
        fedilink
        English
        123 months ago

        That’s a very nuanced analysis. I’ve explained it this way especially to people who describe themselves as “bad at computers”. Hey, give yourself a break, you’ve learned a lot about how to cope with windows. But this investment leads to a conservatism— they dont want to learn coping skills o a new system. The devil you know.

        I’d just add that GUI is more discoverable. When faced with a terminal, what to do? Whereas with a GUI you have a menubar, some icons etc. The GUI gives a lot more hints.

        In the terminal (which I love) it is more powerful once you know how to crack the lid.

        • VindictiveJudge
          link
          fedilink
          English
          23 months ago

          Exactly. You need documentation to figure out how to do anything in a CLI, and if you forget it’s back to the documentation, but a GUI exposes all its commands immediately, allowing the user to find things on their own.

          Except the iOS UI, which is heavily reliant on gestures with varying numbers of fingers, pressure dependent touch commands that are difficult to pull off consistently (seriously, how the hell do you deliberately do the multi-select drag thing?), and hidden menus that are exposed by dragging in from specific portions of the screen at specific angles with no hint that they’re there.

  • @[email protected]
    link
    fedilink
    English
    36
    edit-2
    3 months ago

    Are the “Windows evangelists” in the room with us right now? Every Windows admin I know hates Microsoft with a burning rage. Literally the only people I’ve ever seen promote Windows are being paid to do it.

    Counterintuitively, that’s one reason I like dealing with Windows: the community knows what it is and doesn’t pretend otherwise, like some other more “zealous” fan bases.

    • @[email protected]OP
      link
      fedilink
      26
      edit-2
      3 months ago

      Literally the only people I’ve ever seen promote Windows are being paid to do it.

      Yeah, that’s the demographic I had in mind. Lemmy is full of paid shills lol.

    • Possibly linux
      link
      fedilink
      English
      823 months ago

      The commands: ls cp mv…

      Meanwhile you get Windows people who memorize things like Get-AllUsersHereNowExtraLongJohn

      • @[email protected]
        link
        fedilink
        2
        edit-2
        3 months ago

        In PowerShell most common cmdlets for basic operations have aliases by default. And funnily enough you can use both Windows (cmd.exe) and Unix shell names for these. (copy vs cp, del vs rm, etc.)

        AFAIK The cmdlets that you use only by Verb-Noun convention are mostly used in scripts, or in some administration tasks.

        I also think that some poeple miss the point of PowerShell, as it’s not supposed to be worked with like with Unix shells, since it’s more object-oriented than string-oriented.

        • @[email protected]
          link
          fedilink
          183 months ago

          Versus:

          man $commamd

          PowerShell might be okay script syntax for people with uncorrected sight issues and the elderly who’s heart might not handle bash without set -e but to be useful as a CLI shell prompt that is your primary way of interacting with the computer like it can be on Linux it needs to be so so so much shorter. I’ll be dead by the time I type out half the shit it’d be like 4 key presses total on Linux.

          And that’s before you get to the issues of it being a whole object oriented and typed programming language with .NET whereas shell is nice universal text everywhere that can be piped around however you want.

          There are even those absolute mad lads who unironically use PowerShell on Linux.

          Learning the absolute basics of how to use tmux, vim, sed, awk and grep and pipes and redirects and the basics of handling stdin and stdout genuinely made me feel like all my life I was an NPC in the matrix and now I’m Neo just because passing around bits of text is so powerful when everything works on that basis.

          • @[email protected]
            link
            fedilink
            English
            33 months ago

            Re: length of commands, PS commands are longer, but they also have tab completion so realistically you never type the whole thing, only enough to be unambiguous and press tab. I’ll grant it’s still longer than the equivalent bash, but not by as much as it appears.

          • exu
            link
            fedilink
            English
            23 months ago

            PowerShell doesn’t stop on errors either by default. And of course a significant number of tools you need aren’t available in PowerShell, only cover partial functionality or are an exe you need to call so even if it did stop on error, doesn’t work for those tools by default.

            • @[email protected]
              link
              fedilink
              33 months ago

              It is still a shock to me that some genius aliased curl to Invoke-WebRequest and that curl.exe is what you actually want.

          • @[email protected]
            link
            fedilink
            33 months ago

            I’m one of those that use PowerShell on linux.

            You can use tmux, vim, sed, awk or whatever binary you want from PowerShell. Those are binaries, not shell commands.

            You can use pipes, redirects, stdin and stdout in PowerShell too.

            I personally don’t regularly use any object oriented features. But whenever I search how to do something that I don’t know what to do, a clear object-oriented result is much easier to understand than a random string of characters for awk and sed.

            • @[email protected]
              link
              fedilink
              1
              edit-2
              3 months ago

              Mixing the two philosophies of coreutils and unix bins and whatever is happening in PowerShell seems even more unholy to me than the phrase “object oriented result”, but different strokes.

              I gave up on PowerShell on Windows as a plausible alternative to Bash on Linux the minute I realized there’s no real equivalent tocat, there’s type or if you hate yourself - Get-Content which is aliased as cat but doesn’t really work the same way.

              If I can’t even very basically list a file irregardless of what’s in it, it’s just dead out of the gate.

              On Linux, I once sent myself an MP3 from my server to my laptop with cat song.mp3 | base64 -w0 > /dev/tcp/10.10.10.2/9999 because I cba to send ssh keys.

              I’ll give modern windows a few points - the new terminal emulator application is sweet, and having ssh makes it easy to login to remotely.

              PowerShell is a strange programming language that makes me wish I was just writing C#.

              Bash is a shell language. At its heart it’s a CLI, emphasis on the I, it’s the primary way of interacting with a computer, not a way to write programs. Even awk is arguably better suited.

              That’s why it neither needs to be verbose nor readable for complete beginners, you memorize it the same way you memorize where buttons are on a keyboard or what items you can expect in a right click context menu on Windows.

              Most bash scripts people write are far too complex for it and could stand a rewrite in perl or python or heck, what I think actually works amazing as a “scripting language” - C.

          • @[email protected]
            link
            fedilink
            English
            103 months ago

            Yea, when I switched to Linux, at first I installed PowerShell to get something familiar, but quickly realized that contrary to Windows, terminal on Linux is actually usable on it’s own out of the box.

        • @[email protected]
          link
          fedilink
          English
          23 months ago

          This is me. I’m taking the L on this one and I’ve (at least occassionally) used Unix-like systems professionally for 15 years. I’m all self-taught on Linux and didn’t figure out Tab until I was doing some awful Grub troubleshooting and it spells out that tab autocompletes. So I tried it in terminal and then smirked at the camera like Jim

        • @[email protected]OP
          link
          fedilink
          153 months ago

          I learned that tab=autocomplete when I first played minecraft in grade school haha. I just assumed that it was common knowledge but apparently not…

        • @[email protected]
          link
          fedilink
          123 months ago

          Wait until you learn about fzf - a replacement for ctrl-r that offers fuzzy search with a nice tui

          • @[email protected]
            link
            fedilink
            English
            4
            edit-2
            3 months ago

            I’m completely familiar with fzf!

            I also generally tap in the first few letters of a command then use pgUp (on my system) to autocomplete. Or use the ol’ !<command#>.

            But I have somehow never friggin heard about Ctrl+r.

    • SinkingLotus
      link
      fedilink
      English
      173 months ago

      I’m the type to spend 10 minutes going through my previous commands, rather than 5 seconds typing it.

    • @[email protected]
      link
      fedilink
      English
      73 months ago

      See also: atuin - a shell history tool that records your shell history to sqlite.

      Seamless sync across shell sessions & machines, E2EE + trivially self-hostable sync server, compatible with all major shells, interactive search, etc.

  • katy ✨
    link
    fedilink
    63 months ago

    “i shouldn’t have to memorise commands just to do basic tasks”

    me:

    "a screenshot of the update manager on linux mint"

  • Natanox
    link
    fedilink
    English
    93 months ago

    Think this is more of a accessibility thing. No one denies the CLI is really efficient to use if you’re a professional, it shouldn’t be the norm that you have to be proficient with it to use your computer to the fullest though. Nor to receive help if you don’t feel comfortable using it.

    It would be nice if everyone could enjoy free and trustworthy computing, including people who either can’t or won’t learn many dozens text commands and paradigms.