• carl_dungeon@lemmy.world
    link
    fedilink
    English
    arrow-up
    40
    ·
    edit-2
    8 days ago

    Man, that 1980 machine was a savage beast, most people were rocking’ 32K of RAM at 1MHz, and that 2001 machine was a dinosaur- I had 733MHz G4 in 2001 with 256MB of RAM (pentium 3s were in the 1ghz range I believe too). I think the artist just picked random years and specs.

  • lurch (he/him)@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    31
    arrow-down
    1
    ·
    9 days ago

    the real reason why ppl use CLI is how easy it is to automate and repeat things and chain/pipe commands.

    you can basically just copy a few commands you typed into a text file and run that script later if you need it more than once.

    also most shells have some kind of history. it’s so useful. GUIs don’t have a “do that thing i did last week again” function.

    • lightnsfw@reddthat.com
      link
      fedilink
      English
      arrow-up
      5
      ·
      9 days ago

      Yeah, I recently had to make a bunch of payload files for programming some devices, all the files were mostly the same with only a couple parameters changed. I wrote a script to do it and was done in 20 minutes. That would have taken hours in the GUI. Then when I was putting the files onto flash drives the data protection crap my company uses was blocking part of the transfer because of the extension on the files. So I wrote another script to change the extensions, copy, and change it back. Saved more hours.

    • Cenzorrll@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      8 days ago

      Yeah, I’m not a wizard at the command line or anything, but there are so many things that are just quicker and easier. If I run it enough, I’ll copy the command to a script if it’s complicated, or at least save it for reference later.

        • lightnsfw@reddthat.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 days ago

          Well, kind of. I’ve never gotten a fully usable script out of it for anything complicated. Always have to fix it up myself before it works. Usually gives me a decent starting point though.

    • grue@lemmy.world
      link
      fedilink
      English
      arrow-up
      18
      ·
      9 days ago

      The joke is that touchscreens for desktops will finally catch on by 2034.

    • TrickDacy@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      9 days ago

      Same. I’d also settle for an interesting point too, but apparently all we have here is “nerds be loving terminal”

      • ExtremeDullard@piefed.social
        link
        fedilink
        English
        arrow-up
        6
        ·
        9 days ago

        I suspect this meme was made by someone who never uses the command line, possibly of a younger generation, to poke fun at old-timers. The problem is, everything about is is absolutely correct, making the punchline rather unfunny.

  • elbiter@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    9 days ago

    GUI users haven’t improved that much either. You need a computer 100 times faster and bigger to run the same Excel, the same browser, the same fuckin’ notepad…

    Everything runs in a framework of a framework.

  • hperrin@lemmy.ca
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    2
    ·
    9 days ago

    If you need a program to do something, not look pretty (photo apps, video apps, etc), why include graphics?

    • hitmyspot@aussie.zone
      link
      fedilink
      English
      arrow-up
      23
      arrow-down
      2
      ·
      9 days ago

      GUIs are more intuitive for more people. It’s also nice to be able adjust setting with a drop down or radio, without knowing any commands in a new program.

      That’s not to say cli is bad, or cannot be learnt, but that there are pros and cons.

    • ZILtoid1991@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      9 days ago

      In a GUI application, you can usually just put less often used capabilities into a menu bar, then the user can find it there. In a TUI application, the user will need to spend time to learn it, with the danger of forgetting it. And on the modern AI slop infested web, “Googling” became harder, and I managed to nuke a Raspberry Pi installation from an article that told me how to set paths in Linux.

        • freebee@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          6
          ·
          9 days ago

          Yeah to most people that’s more effort than going through menu’s. Especially people with photographic memory benefit from GUI (don’t remember name of thing you’re looking for but you know where it can be found). Terminal for daily usage is definitely not for everyone.

        • captainlezbian@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          9 days ago

          I knew about <Program> -h but I didn’t know man. And that’s as someone who’s been using Linux for two years and has an engineering degree. Gui is simple in that natural exploration will allow people to intuit where to look for things. Bad gui is worse, as anyone who’s worked with erp software knows, but the command line is less intuitive for exploration for many people and that means they build skills in gui.

          • hperrin@lemmy.ca
            link
            fedilink
            English
            arrow-up
            1
            ·
            8 days ago

            For me, terminal programs make a lot more sense. They’re also easier to make. GUI limits where you can run <program> and what it can do. I mostly code server side stuff, but sometimes I make web and desktop apps, so I’ve got plenty of experience coding them all. I also understand most people don’t want what I want or like what I like.

  • SpikesOtherDog@ani.social
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    9 days ago

    I want to point out that in Windows, it takes about as long to open the disk management snap in as it does to clean, create a partition, quick format, and set a drive letter in disk part.

    In Linux, docker desktop is buggy and causes my containers to crash. Learning to manage them in terminal has been a task, but I seem to have found all the previous functionality and more.

    • shalafi@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 days ago

      Disk Management has always been problematic, breaks constantly, hangs or won’t do the needful. I wrote a PowerShell script to handle all that. Answer some questions, BAM, done.

      • SpikesOtherDog@ani.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 days ago

        I have always seen in the commands for diskpart that it was meant to be scripted. Most of the time when I need it it is a one off or in PE.