• Venomnik0@lemmy.world
    link
    fedilink
    arrow-up
    39
    arrow-down
    2
    ·
    2 years ago

    Honestly, some things can be done faster/as fast on GUI. So really just use whatever increases your productivity.

    • MangoPenguin@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      9
      ·
      2 years ago

      IMO GUIs are always faster when it’s something you’ve never used before, or use very infrequently.

      CLI is better if you’re used to the task you’re doing, or automating things. But for infrequent tasks looking up the commands (or looking at old notes to find it) is very slow and rather annoying.

      • I Cast Fist@programming.dev
        link
        fedilink
        English
        arrow-up
        5
        ·
        2 years ago

        Moving files across several subfolder levels tends to be much faster on a GUI. Finding files is usually much faster via CLI, even when you have to look up again how to use the find command of your choice

        • MangoPenguin@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 years ago

          Is there an instant GUI find tool on linux? find is very slow compared to using Everything on windows, and sorting results is really hard via CLI.

        • Pommel_Knight@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          1
          ·
          2 years ago

          I usually just make a bat or py script to move and create specific files to specific folders.

          I only do this because I’m lazy and numbering, renaming and creating folders is a drag and can be easily automated, but just copy/paste or cut/paste is faster in GUI, especially with alt tab and the new tab file system on windows.

        • CanadaPlus@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          1
          ·
          2 years ago

          A GUI with a search function is always the best way to deal with filesystems, in my experience.

  • r1veRRR@feddit.de
    link
    fedilink
    arrow-up
    26
    arrow-down
    1
    ·
    2 years ago

    To get annoyingly serious on a funny post, the one huge danger of GUIs that I’ve personally witnessed in many of my juniors is that they abstract away the need to understand the tool you’re using.

    I regularly use a Git GUI, and I might have to google the rebase command for more complex tasks, but I know how Git works. I know what I can do with rebase, even if I don’t exactly know how to. If you only live in the GUI, you can get far never understanding the system. Until one day, when you fuck up a commit or a push, and you’re totally hosed because there isn’t a pretty button with the exact feature you want in your GUI.

    • hellishharlot@lemmy.world
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      2 years ago

      Somehow I’ve made it 7 years without messing up a git command that I couldn’t fix in like 2 seconds. I primarily use vscode’s source controller more featured source controllers like sourcetree feel overly complex and typing out git commands is fine but you spend more time doing that than you would with vscode’s approach. I’m really curious about what you mean by fuck up a commit or push

      • BuiltWithStolenParts@lemmy.world
        link
        fedilink
        arrow-up
        6
        ·
        2 years ago

        Try reverting a reverted commit (revert of revert, yes) while other team members are working on a branch which has the first revert. It’s super fun merging after that.

        (Or something of that effect, can’t remember the exact details of that fuckup)

        • hellishharlot@lemmy.world
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          2 years ago

          I don’t think I will, mostly cause I work on a team of 1 right now which makes my branches wonderfully simple.

    • DrM@feddit.de
      link
      fedilink
      arrow-up
      4
      ·
      2 years ago

      Yeah, fuck that. It’s perfectly fine to build a GUI that makes things a bit easier, but make the GUI so that it resembles the fucking workflow. I hate that when I want to automate something thats super easy in the GUI and it takes AGES because there is no equivalent to what I’m doing in the GUI

      • computertoucher5000@programming.dev
        link
        fedilink
        arrow-up
        4
        ·
        2 years ago

        I hate that when I want to automate something thats super easy in the GUI and it takes AGES because there is no equivalent to what I’m doing in the GUI

        glares angrily at Azure CLI

  • Sparrow_1029@programming.dev
    link
    fedilink
    arrow-up
    20
    ·
    2 years ago

    “graphical user interfaces make easy tasks easy, while command line interfaces make difficult tasks possible”

    • William E. Shotts Jr., The Linux Command Line: A Complete Introduction

    It has taken me a long time to get comfortable using a Linux CLI (definitely not as familiar with windows cmd prompt/powershell), and I know that if I log into a box anywhere, If it has sh or bash or some variant of those shells, I’ll be able to get by.

    Now, on my home server, moving & renaming a bunch of media files has me really wishing I had a DE installed there to Ctrl + click/Drag-n-drop…

    Also, I love using VScodium/Code as an IDE bc of its configurability & rich plugin ecosystem – but recently I had some performance hiccups with extensions not playing nice together and started (again) down the masochistic path of configuring neovim to use as an “IDE”…

    • cyruseuros@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      2 years ago

      Skip the masochism, try helix. Switched to that + zellij with about 20 lines of config and never looked back

      • cyruseuros@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        2 years ago

        Takes a second to get used to the keybindings but after about ~2w you can painlessly switch back and forth between vim and helix pretty much instantly

        • cyruseuros@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          2 years ago

          Feel free to ping me if I can help, at least in the form of starter configs/small hacks that emulate VS Code workflows or something :)

          Personally I was the guy that had thousands of lines of Vim and Emacs configurations, so I really had to do this to manage the time sink (like you I had a stint with VS Code in between that eventually stopped working for me)

    • R0cket_M00se@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      17
      ·
      2 years ago

      So far I don’t think anyone has interpreted the meme correctly, the wikiHow guy is supposed to be an obvious shortcoming expressed as a guy trying to convince himself it’s not a problem.

  • jet@hackertalks.com
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    2 years ago

    If you’re using a GUI, that means whatever you’re doing you’re not doing a lot of it, since you don’t need to automate it. I would expect a world-class enterprise engineer to be able to automate most tasks, and from that they would be very comfortable with the command line.

    Can you do everything with a GUI that you can on a command line? Yeah probably, if the developer is at all the features properly. Can you automate it easily? No not at all. So the more you do something the more you tend to want to deal with the vocabulary of the command line because it’s more expressive and allows for automation.

    I will die on this hill!

    • nottheengineer@feddit.de
      link
      fedilink
      arrow-up
      6
      ·
      2 years ago

      Documentation too. Frontends change all the time, but CLI tools usually don’t, so you can usually rely on old documentation. But have you ever tried googling how to do something in MS office, found and article from half a year ago and found that none of the things it mentions exist anymore? It’s ridiculous how much time people waste trying to figure out stuff multiple times because it changes so much.

  • thelastknowngod@lemm.ee
    link
    fedilink
    arrow-up
    13
    ·
    2 years ago

    I think I really only use GUIs if I am learning something new and trying to understand the process/concepts or if I’m doing something I know is too small to automate. Generally once I understand a problem/tool at a deeper level, GUIs start to feel restrictive.

    Notable exceptions are mostly focused around observability (Grafana, new relic, DataDog, etc) or just in github. I’ve used gh-dash before but the web ui is just more practical for day to day use.

    For context, I’m in SRE. I feel like +90% of my day is spent in kubernetes, terraform, or ci/cd pipelines. My coworkers tend to use Lens but I’m almost exclusively in kubectl or the occasional k9s.

        • JackbyDev@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 years ago

          The problem is that they’re all on different servers. Once you use log aggregation stuff like DataDog, Splunk, or Kibana you get it, but before it’s hard to see the benefits. Stuff like being able to see a timestamp of when an error first appeared and then from the same place see what other stuff happened around the same time.

          • Semi-Hemi-Demigod@kbin.social
            link
            fedilink
            arrow-up
            1
            ·
            2 years ago

            If I had dozens or hundreds of servers that would make a huge difference, but for under a dozen I think the cost of setting that all up isn’t worth the added benefit. Plus if the log aggregation goes down (which I’ve seen happen with some really hairy issues) you’re back to grepping files so it’s good to know how.

            • JackbyDev@programming.dev
              link
              fedilink
              English
              arrow-up
              2
              ·
              2 years ago

              Totally. I’m talking more from the enterprise perspective. Even apart from that I’m not sure if the cost is worth it at that scale. Even using foss solutions the dev hours setting it up might not be worth it.

      • thelastknowngod@lemm.ee
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        2 years ago

        You can’t manage pull requests, github actions, repo collaborators, permissions, or any number of the dozens of other things github does just from basic git commands.

  • tvbusy@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    5
    ·
    2 years ago

    PSA: Since his finger and the reflection touches, he’s likely looking into a one way mirror. There’s someone behind the glass.

  • esadatari@lemmy.world
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    2
    ·
    2 years ago

    i feel you bro. people in here talking shit like they don’t know that some net devices are literally made for webgui first and foremost, and programmatic changes don’t work for every api even if it says it’s supported (fucking looking at brocade).

    if you’re used to cisco cli, shit like juniper or palo alto or f5 can be intimidating when looking at the configs.

    but i swear to fucking god if you use gui instead of cli for cisco, we gon have words.

    • Ricaz@lemmy.world
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      2 years ago

      Cisco and Juniper CLIs are terrible imo… Why won’t they just use a proper modern set of tools instead of their own proprietary shit that doesn’t interface with anything else?

      • esadatari@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 years ago

        because cisco fears change and doesnt innovate technologies so much as acquire other companies’ tech and frankenstein it into their portfolio.

        • Ricaz@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          2 years ago

          Had to get some metrics out of an old Cisco box that weren’t available through SNMP, and the only solution I could come up with was to periodically SSH some commands and regex the results.

          That required way too much shell-foo and the SSH daemon would just randomly refuse/drop connections.

          If only there was some kind of standard metric API that every other modern software supports out of the box…

  • kool_newt@lemm.ee
    link
    fedilink
    English
    arrow-up
    8
    ·
    2 years ago

    Both interfaces are important and useful. I spend much time in both and would hate being force to use either for everything.

  • crummysocks@lemmy.world
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    2 years ago

    It’s a different interface for the same thing. Each one has its advantages and disadvantages depending on the job. You should definitely try the CLI if you’re into programming or administration