• ox0r@jlai.luEnglish
      2·
      1 year ago

      Yeah but tbh i really despise powershells syntax. But i’m happy it is pretty powerful.

          • ______@lemm.ee
            1·
            1 year ago

            I hope I didn’t come across as defending ps. PS sucks and whoever decided to have functions use capital case with dashes in between needs to have their brain scanned

            • wizardbeard@lemmy.dbzer0.comEnglish
              0·
              1 year ago

              I do a lot of work in PS and I don’t find it that bad. But you forgot what’s even dumber about their function naming conventions.

              Function names are supposed to be a single word verb, then the dash, then the rest. But not any verb, you’re supposed to use one from PS’s list of acceptable ones which has some really weird omissions. And they break their own single word verb convention with “acceptable verbs” ConvertTo and ConvertFrom (ConvertTo-SecureString, ConvertFrom-Json), which are the only exception to one word verbs before the dash.

              Function names are definitely one of my biggest peeves with it.

              Additionally, their basic comparison operators are dumb as hell. How is “-le” better or clearer in meaning that “<=”? -ne instead of !=, but == isn’t just -e, it’s -eq. And you can’t slap an n in front of other comparators for not, -nle isn’t a thing. You gotta wrap the whole comparison in parentheses and slap an ! on the front or slap -not in front. But don’t try to do !-le, because that’s also not a thing. It’s not terrible but I refuse to believe that -eq is more readable than ==

              • ______@lemm.ee
                1·
                1 year ago

                Functionally speaking, PS is a really good shell language. Its minor things about it that I dont enjoy. As you said, it feels like the language design has some poor decisions.

      • UndefinedIsNotAFunction@programming.dev
        0·
        1 year ago

        I really want to love the “everything is an object” of power shell but I just have zero uses for using a shell on windows. Granted, my windows usage is like 15 minutes a week most of the time, but still. I also can’t be bothered to use it for work because it’s exclusively Linux/linux-ish over there so it’s not worth bothering.

        Either way, I like the idea, can’t really justify figuring out the details.

        • ______@lemm.ee
          0·
          1 year ago

          “But PS is open source ! Don’t you want to use it in Linux and MacOS?” - Microsoft probably

          • wizardbeard@lemmy.dbzer0.comEnglish
            0·
            1 year ago

            It’s a wonderful tool for me in a Windows environment/shop, especially with how it works well with all the Windows and Microsoft administration systems/tools we use.

            Personally, I’m less interested in any language’s hypothetical merits than how it fits as a tool for what I need to accomplish and ease of future maintenance when the script/program/automation inevitably needs to be adjusted.

            All that said, I can’t think of a legitimate reason to use PSCore on non-Windows hardware unless you’re just really familiar with PS and literally nothing else. Even then you’re better off taking time learning a better tool for that environment.

            • ______@lemm.ee
              1·
              1 year ago

              That’s a very good point. My angle is as a dev and not as IT or sys admin. Power shell is probably far more powerful in those circles.

    • jasondj@ttrpg.network
      0·
      1 year ago

      Still won’t help me when I type ifconfig or dig, though.

      Also I’ve noticed there is also a curl in Windows CLI that I believe is based on libcurl, but when called from powershell is an alias for (iirc) Invoke-WebRequest.

      • jvisick@programming.devEnglish
        0·
        1 year ago

        I came across this one just yesterday and while it was convenient at first, I immediately got frustrated when I went to add some parameters and discovered it wasn’t actually curl

        • JustBrian7872@feddit.de
          1·
          1 year ago

          Classic PoweShell experience. Try rm -rf - I wonder why they added the aliases in the first place. Only frustrating to type different arguments which are also more verbose. Tastes like the good ol’ embrace-extend-extinguish.

  • voxel@sopuli.xyz
    1·
    1 year ago

    use powershell (specifically the core version!!!), or even better something like Nu shell

  • over_clox@lemmy.world
    0·
    1 year ago

    echo @dir %1 %2 %3>%windir%\system32\ls.bat

    Something like that should fix the problem, I think…

    • captsneeze@lemmy.one
      1·
      1 year ago

      As of Aug 26, 2023, Windows command prompt absolutely does not recognize “ls” as a command.

      Powershell is a different story.

      Source: I type “ls” 40 times a day into a command prompt on my up-to-date win10 PC at work.

      • icesentry@lemmy.ca
        0·
        1 year ago

        Out of curiosity what do you do to frequently end up with cmd? I don’t think I’ve touched it in many years at this point.

        • mateomaui@reddthat.comEnglish
          1·
          1 year ago

          Lately I’ve been using it as a simple way to drag and drop a source .tar.xz archive on a .bat file so it can be twice extracted, moved, renamed, have dependencies downloaded by git, run a cmake process, do a visual studio compile, then move the result release directory back to where the .bat file is while removing unneeded files and adding new ones.

          cmd and batch still has its uses.