• @[email protected]
    link
    fedilink
    302 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.

    • @[email protected]
      link
      fedilink
      52 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

      • @[email protected]
        link
        fedilink
        42 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

        • hellishharlot
          link
          fedilink
          22 years ago

          Azure CLI and AzPowershell are somehow so powerful and useful until they fall flat on their face.

    • hellishharlot
      link
      fedilink
      72 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

      • @[email protected]
        link
        fedilink
        72 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
          link
          fedilink
          32 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.

  • @[email protected]
    link
    fedilink
    English
    212 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.

  • Marxism-Fennekinism
    link
    fedilink
    English
    9
    edit-2
    2 years ago

    Use a computer in whatever way you want and/or need to best get the job done. It’s a tool for accomplishing tasks. The amount of random gatekeeping for no goddamn reason in tech/programming/FLOSS is ridiculous.

    • @[email protected]
      link
      fedilink
      92 years ago

      But you look way cooler when using the terminal for most of your stuff 💁‍♂️ also using a riced out window manager and riced out Vim config for which you spent hundreds of hours on customizing every aspect of it :p normal people don’t know what the fuck is going on on your pc so you can feel instantly feel superior to those normies! Ah also btw i use arch ;)

    • beneeney
      link
      fedilink
      92 years ago

      I use both. I use the CLI for a lot of stuff but I also use the GitHub Desktop fork for Linux lol. I don’t care how powerful git is in CLI, that gui is just so nice imo

      • @[email protected]
        link
        fedilink
        62 years ago

        It took me forever to realize I could edit config files in a graphical text editor. When you have a really long file it’s just nicer to have properly formated text wrapping and a scrollbar with a preview box.

      • @[email protected]
        link
        fedilink
        52 years ago

        Exactly. Use the tools you have the way they fit you best. If it aids your work flow learn the CLI commands you use the most. If it’s something obscure or rarely used, use the gui.

        Another not mentioned benefit of becoming comfortable with using the cli is that you then can more easily script stuff.

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

        It’s what you put on bad software to make it palatable.

        Like a sugar coating. It’s why no one codes in Java anymore without 80 terabytes of ram for their IDE.

        • @[email protected]
          link
          fedilink
          32 years ago

          I wonder what’s this “good software” (you meant language?) that doesn’t require an IDE to code efficiently.

          • @[email protected]
            link
            fedilink
            32 years ago

            Good luck ever doing anything embedded if you always need a clunky IDE. Best thing I ever did was get comfortable in a solely vim/cmake/gcc environment. Even if the majority of work doesn’t require it, it’ll teach you a lot.

            • @[email protected]
              link
              fedilink
              12 years ago

              I mean, we’re rewriting everything in Rust, so there’s no need to learn cmake anymore /s

              To conter your comment a little bit, I think anyone doing coding for a living should absolutely use an editor that supports LSPs. They’re an insanely helpful tool with zero downsides.

              • @[email protected]
                link
                fedilink
                22 years ago

                I installed an LSP in neovim and it mostly just annoys me and clutters my screen while i’m typing.

          • @[email protected]
            link
            fedilink
            12 years ago

            I disagree somewhat with their take, but there’s definitely languages that cmoe with features built-in that reduce the need for a fancy IDE. For example, instead of null checks via annotations that the IDE has to parse and warn about, just have nullable types. Or instead of IDE features to generate a bunch of boilerplate, just don’t require that boilerplate.

            That being said, on the other side of the spectrum, anyone writing code without using an LSP is just throwing away productivity by the handfull.

        • @[email protected]
          link
          fedilink
          English
          12 years ago

          So that’s my point. Don’t write or use bad software. Then the GUI (bad or good) isn’t necessary.

  • nik0
    link
    fedilink
    482 years ago

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

    • @[email protected]
      link
      fedilink
      532 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
        link
        fedilink
        English
        162 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

        • @[email protected]
          link
          fedilink
          English
          42 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.

            • @[email protected]
              link
              fedilink
              22 years ago

              I am but searching via CLI I’m not sure how to easily sort by last modified time, or restrict to a specific root path first.

          • KubeRoot
            link
            fedilink
            22 years ago

            I don’t know about GUI tools, but:

            Everything is so fast because it uses the index built into NTFS to find files by filename quickly, and NTFS is the definitive file system on Windows so it works everywhere.

            On Linux, there isn’t really an index built into the filesystem - some might have that, but I don’t know about it. That said, plocate is a common tool that uses its own index. You have to update the database when files change (you’ll probably have a job doing that daily), but searching the index is very fast.

        • @[email protected]
          link
          fedilink
          English
          12 years ago

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

            • @[email protected]
              link
              fedilink
              22 years ago

              Your filesystem must be monstrously huge if it’s actually perceptibly slow. I also get tired of typing in long filenames with a ton of special characters I have to escape.

              • @[email protected]
                link
                fedilink
                12 years ago

                You’ve never had to search through hundreds of gigabytes of source files, I guess. Congratulations.

                • @[email protected]
                  link
                  fedilink
                  12 years ago

                  No, I’ve never had that displeasure, Nothing I’ve worked on has been that big. My condolences.

        • Semi-Hemi-Demigod
          link
          fedilink
          42 years ago

          The more you use the commands the more you remember them. I got good at the CLI by forcing myself to use it for things I would normally do in a GUI. Now everyone thinks I’m a wizard which I won’t discourage

        • @[email protected]
          link
          fedilink
          12 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.

    • R0cket_M00seOP
      link
      fedilink
      English
      182 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.