• SpaceNoodle@lemmy.world
    link
    fedilink
    English
    arrow-up
    26
    ·
    2 months ago

    Great, now I’ll have to Google Bing for a four-line command when before I could just dig through a few menus.

    • Beacon@fedia.io
      link
      fedilink
      arrow-up
      12
      arrow-down
      1
      ·
      2 months ago

      I mean, if there’s still gonna be command line commands for all the features then there’s no reason why a 3rd party couldn’t make a gui app for them and recreate the control panels app

        • NaibofTabr@infosec.pub
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          1
          ·
          2 months ago

          Actually PowerShelll is basically a wrapper for .NET classes… and it doesn’t really emulate Bash in any functional way.

          • xavier666@lemm.ee
            link
            fedilink
            English
            arrow-up
            6
            ·
            2 months ago

            The little time I have spent on powershell, I found it to be very slow. The input is also very verbose. I’m sure someone will say it allows one to be specific but I can be equally specific in bash as well. It’s like the Java Enterprise of scripting language.

            • NaibofTabr@infosec.pub
              link
              fedilink
              English
              arrow-up
              6
              arrow-down
              2
              ·
              edit-2
              2 months ago

              It is verbose. It’s intended to be readable by untrained people, with a consistent verb-subject format for commands (e.g. Get-ChildItem, Set-Variable), though it turns out that concept doesn’t scale very well and the format gets increasingly broken when you get into the Azure PowerShell commands (New-AzLoadBalancerInboundNatRuleConfig).

              The real power of PowerShell is that it can interact with .NET directly (because it is .NET), which allows you to quickly and easily build scripts for anything that uses .NET (like Windows). For instance, you can view or edit registry keys of other systems through a PowerShell remote session (using the .NET RegistryKey class), and set up a loop to edit a registry key across a list of machines remotely (I used to do this while managing on-prem AD groups in my last job, it’s much faster and easier than trying to change registry keys through remote desktop sessions, more reliable because it’s programmatic, and you can easily log the command output and catch any systems that failed to accept the change).

              PowerShell might not be what Bash is for the average Linux user, but it’s a massive improvement for managing Windows systems at scale. Anyone who works in corporate IT should learn PowerShell.

              • xavier666@lemm.ee
                link
                fedilink
                English
                arrow-up
                2
                ·
                2 months ago

                For instance, you can view or edit registry keys of other systems through a PowerShell remote session (using the .NET RegistryKey class)

                It’s like a built-in Ansible equivalent (the configuring and management part at least). I’ll agree that’s neat. If I managed a fleet of Windows machine, I would properly learn that.

                But I don’t think it’s something for the average home user. And the Linux way of configuring remote machines is too easy.

        • Matriks404@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          3
          ·
          2 months ago

          Powershell has a completely different approach of working with commands than traditional Unix shells. You pretty much don’t know what you are talking about.

            • Matriks404@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              arrow-down
              2
              ·
              2 months ago

              That’s fine, I also pretty much prefer standard Unix tools, due to how efficient they are, but you can’t just say made up stuff with no valid explanation, because Powershell has still nothing to do with bash.

    • Matriks404@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      2
      ·
      2 months ago

      Powershell at first seems to be weird and clunky, but after you get used to its syntax you can quickly look up and use its commands without much guessing.

      • SpaceNoodle@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        1
        ·
        edit-2
        2 months ago

        No, it’s already more usable. You’re not bound to a GUI or hidden, indiscoverable incantations.

        • richmondez@lemdro.id
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          I felt the /s was implied but clearly enough people actually believe that linux is only for people who master arcane command lines that it could be taken as a genuine belief.