• emberinmoss@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    It’s different, it’s unfamiliar territory and I’m pretty dumb. But I need it. I need to get on that linux like a fish needs water. I will be joining the linux soon enough, or so help me God.

  • Kuranashi@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    I’ve never met any windows evangelists to be honest. Lots of Apple evangelists though who will spend forever talking about windows. Every developer I’ve met who uses Windows always had a tongue in cheek sort of “well it kind of sucks in some ways but it’s what I’m used to, one day maybe I’ll get off my ass and change OS”.

    Reminds me of the “I use Arch Linux btw” meme which doesn’t really happen as much anymore other than as a joke. Also, I use Arch Linux btw

    • shortrounddev@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      Im not an evangelist for windows (I won’t try to convert you) but I’m unashamed of being a software engineer who uses Windows as my main dev platform

        • shortrounddev@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 months ago

          At work everything I do is in the Javascript/Web world. Typescript backend, webpack react, etc. I use C++ and C# for personal projects because I personally despise Javascript world

          • Kuranashi@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            2 months ago

            That’s like my opposite haha, all my own projects are TypeScript and vite react, at work I was working with C#. Though I do prefer static typing much more.

            • shortrounddev@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              2 months ago

              When I work on web projects at home I don’t use any javascript at all. Just html and css. Interactions are handled via form submission. I’m working on a forum in asp.net mvc without any javascript at all

    • ftbd@feddit.org
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      There are definitely people who think it is reasonable to memorize button locations and 10 levels of menus in GUI programs but would rather go into cardiac arrest than use something like program --option input-file output-file.

      • Oniononon@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        2 months ago

        thing with gui is you don’t need to memorize button locations and menus. If you do it’s poor layout. Good gui lets you find things you didn’t know you were looking for intuitively, without external resources or manual. CLI requires you to know what exactly you are doing and is impossible to use without external resources. Nothing against terminal but unless you know what you are doing and every command required to complete that action, it’s ass. If gui was so bad and cli was so good, guis would not be used by anyone.

        I mean you dont go around copy pasting device ids and running commands for 20 minutes to connect your device through terminal when it is done with 2 clicks in the gui even by someone who has never used a pc before.

        • Ziglin (it/they)@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          To be fair if you want to learn your options (without properly informing yourself using a manual) tab complete can be useful if implemented.

          Also most programs come with their manuals so I’d barely call it external. The manuals are also usually better than what I’ve come to expect from the text to go with buttons in a GUI.

          Knowing what commands are required is always going to be necessary but there’s also not that many worth remembering.

    • JayDee@lemmy.sdf.org
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      2 months ago

      It’s not that they are mad others use CLI, it’s that they’re mad that Linux devs regularly stop creating P&CI features, instead opting for CLI with no P&CI equivalent action.

      It’s kind of obvious why - CLI is already very flexible right out of the box, and it takes much less work to add functionality within CLI rather than creating it for the P&CI.

      At the same time, I understand the P&CI folk’s frustration, since one of biggest obstacles to getting more people on Linux is the lack of P&CI solutions, and the fact that many actions on Linux are explained solely via CLI.

      CLI folks have invested the time to use terminals effectively and view overuse of the P&CI as beneath them, and P&CI folks have no interest in dumping time into learning CLI to do something they could do on Windows with P&CI.

      • pinball_wizard@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        2 months ago

        they’re mad that Linux devs regularly stop creating P&CI features, instead opting for CLI with no P&CI equivalent action.

        I’ve never seen this?

        It’s typically a completely different developer who creates the CLI first, and then one of us adds a P&C after.

        So if something is brand new, sure there might be no P&C, yet.

        I promise There’s no conspiracy to not have nice things. Haha.

        • JayDee@lemmy.sdf.org
          link
          fedilink
          arrow-up
          0
          ·
          2 months ago

          I was specifically trying to not sound conspiratorial. I’m pointing out that it’s a matter of having learned a paradigm vs having to learn a new paradigm.

          Devs have already gotten used to CLI and very rarely make full P&CI suites because of it. Even if the original Dev only did CLI for the app and someone came back and made a P&CI for that app, those P&CI interfaces are still fairly barebones. This is both a mix of devs knowing how good CLI can be and because it’s all open source volunteer work.

          Layman users of P&CI-focused DEs actively avoid CLI so they don’t have to learn it. This means that using most Linux apps are something to be avoided for most Windows users, making the OS base mostly unusable for them.

          To be clear, when I am talking about P&CI-focused DEs, like windows and iOS, I mean that if you cannot perform an action with the P&CI, then that action essentially does not exist for the average user. Contrast that with Linux DEs, where it’s quite common to have to directly edit configs or use the CLI to perform various actions.

          As a veteran user, CLI does not bother me. I do understand the frustration of those who want some Linux DEs to become as default as Windows and iOS, because lack of P&CI does damage that effort.

          This is not every app in Linux obvi, but the ones that are best at making sure the P&CI is full-flddged, are the apps that develop for windows and iOS as well as Linux - Blender, LibreOffice, Logseq, Godot, etc. The most common offenders are the utility apps, such as those that handle drivers, sound systems, DE functions, etc.

          • pinball_wizard@lemmy.zip
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            2 months ago

            This means that using most Linux apps are something to be avoided for most Windows users, making the OS base mostly unusable for them.

            I take your point. And this was very much the case for a long time.

            But it’s worth pointing out that Gnome and KDE are both done, now.

            I haven’t been forced to reach for command line to change something - anything - on either of my last couple of Linux installs.

            Edit: I almost didn’t notice, but it feels worth celebrating and raising awareness.