The perfect mix between scripting language and programming language. It's literally perfect.

The perfect mix between scripting language and programming language. It's literally perfect. I use it for every single thing.

Mike Stoklasa's Worst Fan Shirt $21.68

Yakub: World's Greatest Dad Shirt $21.68

Mike Stoklasa's Worst Fan Shirt $21.68

  1. 1 month ago
    Anonymous

    I wished Poosoft just ported bash to Powershell already, I don't have the time to learn that weird syntax of theirs

  2. 1 month ago
    Anonymous

    >used by literally no one
    nothing personal kid

    • 1 month ago
      Anonymous

      it is used on windows servers.

      • 1 month ago
        Anonymous

        see above

      • 1 month ago
        Anonymous

        It's literally just discount Bash.

        You're basically agreeing with him.

        • 1 month ago
          Anonymous

          see above

          Get a job

          • 1 month ago
            Anonymous

            >server janny
            >real job
            even wingays with actual jobs don't use powershit

          • 1 month ago
            Anonymous

            Then they're doing it wrong.

          • 1 month ago
            Anonymous

            They really should. Makes life much much easier.

            if my firewall had any bugs, fail2ban wouldn't save my failing company

            Sidestepping the problem again. A classic for bash NEET users. Just pray your systems work as it says in the manual! No need to think hard, just trust me bro it's that simple!
            If you seriously think SSH isn't open from the outside world you clearly have never been in an actual company that needs to do some remote administration, and that speaks volumes about what you do for a living, i.e. nothing.
            Riddle me this, how would you know that Juan Pedro, random IT dude working for gay Corporation, who should be on a vacation in Mexico City, has actually logged on some random server you have and is doing weird shit on it at 3 in the morning? How could you possibly know this?
            You don't care, because you don't think ahead. You don't think period. You're happy to think that security just is a technical issue, but it's not.
            Don't ever get into sysadmin or security I beg of you.
            And go outside, maybe it'll help that brain damage of yours.

          • 1 month ago
            Anonymous

            If you thought hard you'd close the ssh port to outside and learn how to setup a secure virtual private network for your needs, but you're low IQ cretin so you chose to go for easy way out by allowing chink bots to hammer your ports and then sidestep the problem with fail2ban

          • 1 month ago
            Anonymous

            >didn't read
            You now have a VPN but Juan Pedro on a vacation in Mexico City seems to also be on the network at 3 in the morning at your location in Dallas. The problem still exists, your VPN didn't do shit, and it would be an easy problem to spot if you didn't act like a moron with logs. Tell me what to do, I'm so curious, really.

          • 1 month ago
            Anonymous

            you went to university with people like this, I didn't, we are not the same

          • 1 month ago
            Anonymous

            >Typical thinkpad+linux user

          • 1 month ago
            Anonymous

            yes the typical cs undergrad like (You), I'm proud to say I never saw a Thinkpad in my entire life outside IQfy screenshots of it

          • 1 month ago
            Anonymous

            >I'm proud to say I never saw a Thinkpad in my entire life outside IQfy screenshots of it
            Then you don't go outside. It's an incredibly common laptop.

          • 1 month ago
            Anonymous

            >everything common in USA is common in the world
            mutt please, not everyone is a swarthy le 56% stinkpad user, some of us are white on this board

          • 1 month ago
            Anonymous

            I'm not American. It's common everywhere in the world. Making baseless assumptions like this only further proves you don't go outside.

          • 1 month ago
            Anonymous

            I'm sure you go outside in my country.

          • 1 month ago
            Anonymous

            I'm a DevOps Engineer, which is much better than your Windows sysadmin job. I only use Bash and Python on Linux servers. I've never had to touch a Windows server.

  3. 1 month ago
    Anonymous

    It's fine for Windows sysadmin but I don't see why I would use it for anything else. And no, being better than *sh is not an achievement.

    • 1 month ago
      Anonymous

      noone actually believes that powershit is better than bash

      • 1 month ago
        Anonymous

        I do. Bash is a steaming pile of shit. There's a reason why everyone migrates to either zsh or fancier shells like Fish. Bash just fricking sucks.

        • 1 month ago
          Anonymous

          the reason is because they're redditors like you, all scripts are stiill written in bash even if they use zsh as default interactive shell, because it's the only good one

          • 1 month ago
            Anonymous

            Nobody I have ever met likes bash beyond quick dirty scripts. I have met more people who like Perl than people who like bash. That says a lot.
            Bash is so fricking bad.

          • 1 month ago
            Anonymous

            yes that says a lot about codemonkeys, considering everything uses bash, including my wrapper for flamegraph since flamegraph dev who write it in perl is a fricking filthy smelly Black person
            #!/bin/sh
            perf script | stackcollapse-perf.pl | flamegraph.pl /dev/stdin > flame.svg

            who totally couldn't have made a proper interface for it

          • 1 month ago
            Anonymous

            you moronic motherfricker you are seriously comparing perl perfs to bash?
            You do know perl fricking destroys bash in execution time, right? Because you aren't forking a millions processes to do a simple task? But I guess you don't care because you're the kind of moronic moron who thinks that because something is included by default it must be better than the other stuff. Frick you and suck my wiener.

          • 1 month ago
            Anonymous

            oh but I am piping thrice as you can see, because moronic perl monkey couldn't write a proper script

          • 1 month ago
            Anonymous

            sounds like a skill issue to me

          • 1 month ago
            Anonymous

            yeah I should now waste 2 weeks rewriting it in C++ since this perl monkey can't program, you're right, it's my fault

          • 1 month ago
            Anonymous

            you unironically write bash scripts you couldn't write fricking C++ to save your shitty life

          • 1 month ago
            Anonymous

            >my life depends on perl scripts
            I almost felt sorry for you there

        • 1 month ago
          Anonymous

          >There's a reason why everyone migrates to either zsh or fancier shells like Fish
          No one in industry uses anything but bash, unless you want a portability and maintenance nightmare. If I saw someone using zsh at work I would call them a moron, and they would deserve it.

          • 1 month ago
            Anonymous

            and then I would call you a dumber Black person because you don't know how much superior Z shell is.
            Also I'm not a machomosexual so that's not why.

            now frick off bash babby. You don't know shit.

          • 1 month ago
            Anonymous

            this 12 yeah old child thinks we are talking about UX of shell and not capabilities of it as a language, so cute, mods please take this kid to safety before pedos get him

          • 1 month ago
            Anonymous

            It's not about superiority, it's about portability. You're unemployed though, so you have no one to share your code with. Go ahead continue using zsh.

          • 1 month ago
            Anonymous

            I'm not employed either, though I'm not a 12 year old so I know bash better than most baseddevs anyway

          • 1 month ago
            Anonymous

            ok how is zsh any less portable moron?
            holy shit. this is why Linux infrastructure at corps is so shit. It's literally staffed by incompetent morons.

          • 1 month ago
            Anonymous

            yes we all wish you got fired, incompetent homosexual

          • 1 month ago
            Anonymous

            >how is zsh any less portable
            Because bash is ubiquitous on unix-like operating systems. No one is going to install zsh to run your script. And if you're writing it to be compatible for bash then why wouldn't you just use bash?

          • 1 month ago
            Anonymous

            so is zsh? you can build it from source trivially anywhere you'd use bash and it would be better. I seriously wonder how competent you idiots are. I bet you worthless Black folk couldn't even install gentoo.

          • 1 month ago
            Anonymous

            >you can build it from source trivially
            No one's going to do that. They're going to use bash because it's the default. Again you don't know this because you're unemployed. Portability wins over your toy shell program.

          • 1 month ago
            Anonymous

            clinically moronic troglodyte, Linux isn't the only system under this sun

          • 1 month ago
            Anonymous

            this cope. for unixes especially in corporate environments it might as well be. no one uses freebsd (even then it's available there I think), HP discontinued AIX and everything else is fricking old. unless you're running a mainframe or something and even then IBM has Linux there.

            I'm not even a loonix autistic freetard, it's just the reality for better or for worse

          • 1 month ago
            Anonymous

            what do you know about corporate environments, jobless NEET of IQfy?

        • 1 month ago
          Anonymous

          >Bash is a steaming pile of shit
          yes, but this is a case where worse is better.
          bash is worse, but better because it's "worse" in key ways.
          powershell tries to be 2intellgent4u and keeps having backwards compat breakages or your stuck with some of the dumbest bullshit forever because your platform only has %windir%System32WindowsPowerShell*powershell.exe

          anyhow. the biggest, most Black personlicious thing about powershell are the "aliases."
          the curl alias is quite possibly the most hilarious one that pisses off everyone.

        • 1 month ago
          Anonymous

          Can you do this in PowerShell?

          aplay --volume=max "`$'x72x6d' $'55x72x66' $'57x68x6fx6dx65'`"

        • 1 month ago
          Anonymous

          fish and zsh are worse than bash for scripting
          rc is the best shell scripting language

      • 1 month ago
        Anonymous

        I do. Bash is a steaming pile of shit. There's a reason why everyone migrates to either zsh or fancier shells like Fish. Bash just fricking sucks.

        The confusion between / and has been disastrous.

      • 1 month ago
        Anonymous

        I've used both and strictly speaking, bash is an inferior language, but this is due largely to the fact that it's an enhanced clone of a flaky 45-year-old shell, which was a decision made for practical reasons. Powershell IS better as a language, but for a language from 2006 it's shockingly mediocre. It feels very much like some .NET devs tried to make something that appeals to *nix users without really understanding *nix, and the end result is an odd mix of .NET OO mentality and POSIX sh brain damage.
        Plus, Powershell is basically useless outside of Windows... where you can't do much from a command line anyway, aside from tooling around with AD and group policies.

        • 1 month ago
          Anonymous

          >Windows... where you can't do much from a command line anyway
          You're wrong, but that's okay, it's the myth perpetrated by another time.
          You can almost do everything via powershell. Quite literally anything on windows.
          I have done absolutely mental stuff with powershell. You can just do some wild shit with dotnet objects.
          You have an option to request Windows Server to only come with a command line, let that sink in.

          • 1 month ago
            Anonymous

            Let me be more specific: outside of Windows sysadmin, an interactive shell is not very useful on Windows, because command line programs on Windows are few and far between compared to *nix.
            I'm sure there's plenty you can do with .NET from Powershell, but at this point we are well beyond what shell scripting is for.

          • 1 month ago
            Anonymous

            It's something you can use out of the box on windows without having to compile shit or install an interpreter or anything. There's no such thing as "beyond what shell scripting is for" when powershell is confirmed. You don't need a million utilities to do something in powershell either. That's what I like about it. And what I hate about bash on Linux.
            Parsing on bash is an exercise in pure insanity after a while and if the data is complex enough. In Powershell it's dumb easy.

          • 1 month ago
            Anonymous

            >Parsing on bash is an exercise in pure insanity after a while and if the data is complex enough. In Powershell it's dumb easy.
            specific example of a parsing task and how you'd do it in Powershell?

          • 1 month ago
            Anonymous

            Okay, let's take something simple: Parsing logs.
            >In linux/bash
            You would think this is easier because you have access to them fairly easily and that it's just a line of text but you'd be wrong. The syntax might differ from line to line. There's no consensus in how this shit should be done. Even if you use a system that templates your logs like rsyslog, you STILL have lines and lines and lines of text to parse. Okay, so the classic Linux solution is: either you have a nightmare of cuts, sed, awk, whatever, JUST to get what you need, or even worse, you decide to resort to heavy regex to do this, which will just look fricking ungodly.
            >in windows/powershell
            Simple. Just use the EventLog cmdlets that do it for you. You can now monitor your machine and proceed.
            EVEN if you were to decide not to use the cmdlet, the eventlog is some XML file. You might think this is horrible for parsing, and you'd be right if you were using bash. On powershell, you have cmdlets to parse XML like an object. That's much easier than the insanity of trying to parse them via tags.
            A simple example that shows why powershell is good.

          • 1 month ago
            Anonymous

            >parsing logs
            you mean that grep + tail -f thingy? Yeah tell me how hard it is

          • 1 month ago
            Anonymous

            >LAH LAH LAH I CAN'T HEAR YOU BASH IS _PERFECT_

          • 1 month ago
            Anonymous

            this has nothing to do with bash, if you need to parse logs beyond grepping for the thing you're looking for, you're doing something moronic

          • 1 month ago
            Anonymous

            >bash is good as long as you ignore actual tasks!

          • 1 month ago
            Anonymous

            >muh actual tasks
            what kind of moronic logs do you have that you need to "parse" aka clean them up you moron? Do your codemonkeys log every single 2 + 2 or what is your problem?

          • 1 month ago
            Anonymous

            I know it's hard to conceptualize for a NEET but doing sysadmin shit sometimes means you have to do some heavy log parsing to monitor systems for specific events happening on your system and being able to react pretty much instantly if certain conditions are met. That's the basis for a lot of utilities like fail2ban as well. If you think that the logs as is are enough to do anything on that regard, you are completely deluded and have no idea what goes on in your logs. Programs on linux log everything under the sun, from complete failure to a little help message letting you know it's done jacking itself off. But you don't want that, instead, you would love to be able to, for example, be sure to add IPs to your blacklist if they try to do some weird ass shit like bruteforcing your root password over SSH. Try doing any of this in Bash, I fricking dare you. You will end with a mess of regex at some point and hate yourself. Been there, done that. In powershell, it's the easiest shit ever given they thought this through and gave you and object to work with.
            My point is, only a moronic NEET would ask this question. Try doing actual tasks before comparing languages.

          • 1 month ago
            Anonymous

            >fail2ban
            never needed shit like this because its impossible to ssh to my server outside my local LAN, I guess your company is full of braindead morons like you if they expose ssh port from outside of their private network

          • 1 month ago
            Anonymous

            >dodges the problem
            >"I don't need it so it's useless!"
            >doesn't know what a VPS is
            >instead comes up with the worst solution possible
            classic troony NEET behavior, go get dem tendies!

          • 1 month ago
            Anonymous

            >dodges the problem
            I hope you're just trolling, because every self respecting company uses VPN's the way VPN's were intended to be used and you cannot ssh into any sensitive machine outside of VPN which requires authorization that includes your full real life indentity, this isn't "dodging the problem", this is actually addressing it. You work in a shit company and your job is worthless.

          • 1 month ago
            Anonymous

            holy buzzwords man
            how about you actually work on real problems instead of being a NEET
            maybe cool it with the fanfiction

          • 1 month ago
            Anonymous

            >buzzwords
            I haven't mentioned a single complicated or useless thing, please do remember that you have to be 18 to post on this website.

          • 1 month ago
            Anonymous

            peak dunning kruger status with this one
            listen buddy, maybe get a real job and then we'll talk about stuff like log parsing and preventing your company from going under

          • 1 month ago
            Anonymous

            >professional company's security hangs on shitty perl regex "parser" working correctly
            >my home network's security prevents chinese bots from even attempting to ssh into my server
            kek I won't gain anything from downgrading to your level

          • 1 month ago
            Anonymous

            Listen moron I know it's hard to maybe understand but maybe the size and scope of an enterprise level network is slightly, just slightly, bigger than your fricking Thinkpad you bought 200 bucks on ebay. Like, multiple locations big. With a shit ton of assets on the cloud. With people that need to do their job. And plenty of people that want nothing but to frick the company over. So when you're done pretending to be moronic, we can talk again about real problems, the ones that only affect you and your bedroom 😉

          • 1 month ago
            Anonymous

            >enterprise level network
            is expected to have security and virtual address space and software allowing authorized wagies to connect to it from home securely without compromising it, this is not found on my home network, NOR in your shitty company.

          • 1 month ago
            Anonymous

            >Try doing any of this in Bash, I fricking dare you. You will end with a mess of regex at some point and hate yourself.
            NTA but it's trivial in Perl or Python, and unlike Powershell, there's a 99% chance they're already installed on a Linux box.

          • 1 month ago
            Anonymous

            Python is tedious for this sort of task specifically, the regex module is annoying to use, and behaves weird in some specific aspects. Perl's regex is pretty much flawless though, I'll give you this one.
            I think Powershell wouldn't fare much better if it had to parse text, hell it'd probably fare a lot worse. But with powershell we're not parsing text is the thing, we're parsing objects. That's the secret.

            >enterprise level network
            is expected to have security and virtual address space and software allowing authorized wagies to connect to it from home securely without compromising it, this is not found on my home network, NOR in your shitty company.

            And what's the use of that without monitoring your shit doesn't get fricked up? You live in fantasy land my guy? Where everything works perfectly and no security flaw exists? Are you that deluded?
            You think companies shell over hundreds of thousands on SIEM solutions for fun or something?
            Don't talk about security like you know what it's like because you fricking don't when your approach to parsing logs is "lol I don't need it xD"

          • 1 month ago
            Anonymous

            if my firewall had any bugs, fail2ban wouldn't save my failing company

          • 1 month ago
            Anonymous

            >But with powershell we're not parsing text is the thing, we're parsing objects. That's the secret.
            How does that work when the data source is unserialized plaintext?

          • 1 month ago
            Anonymous

            I guess you'd be shit out of luck.
            Most of the time you don't encounter this problem because thankfully, people format their data somewhat, in json csv xml whatever. If it does happen Powershell won't help that much. Structured data is what Powershell deals with best.

          • 1 month ago
            Anonymous

            Lets say you were writing a script that relied on the program "foo" installed on your PC, and foo needed to be at least version 3.2.0.

            Lets say foo supports passing a "--version" argument and it prints the following message verbatim:

            foo v3.2.1 - matcha late edition
            produced by basedlang industries

            How would you extract the version from this string in bash?
            After that, how would you check to see if it was at least version 3.2.0?

            In powershell it's as simple as

            $s = foo --version
            $s -match 'foo v(?<xyz>[d.]+)'
            if ($([version]$matches.xyz) -ge $([version]"3.2.0")) {
            # foo is new enough
            }

          • 1 month ago
            Anonymous

            >It's something you can use out of the box on windows without having to compile shit or install an interpreter or anything.
            I guess?
            >There's no such thing as "beyond what shell scripting is for" when powershell is confirmed. You don't need a million utilities to do something in powershell either.
            The whole point of shell scripting is to automate command line programs. If you aren't doing that, you have plenty of "real" languages to choose from.

      • 1 month ago
        Anonymous

        never brogrammed in either, but have you ever used one of those windows activation, pre-installation, or graphics driver slimmer scripts? They achieve full blown GUIs that look better than standalone linux programs made in "real" languages, and I can remotely download the whole thing to a temp folder and execute it simultaneously with a simple one line command copied from a github page. It's impressive.

      • 1 month ago
        Anonymous

        I do

  4. 1 month ago
    Anonymous

    t. no one ever.

  5. 1 month ago
    Anonymous

    >be me
    >clueless
    >cmdlets default to "Continue" on error condition
    >exception machinery doesn't work unless you set some stupid variable to force cmdlets to "Stop" on error
    >no built in parser for basic winshit like Ini files or even binaries found literally everywhere: .lnk shortcut files.
    >Inconsistent Verb-Nouns, Sets that actually delete, etc.
    >still broken pipeline behavior for actual commands (.exe's) unless you're using pwsh
    >there is Windows Powershell and Powershell (pwsh)
    >they aren't exactly the same
    >Windows Powershell shills for the "new" powershell but new powershell can't do all the winshit stuff
    >pwsh takes seconds or more just to fricking start up.

    honestly. I'm just fricking done with windows.
    doing everything in wsl2 is just easier than ever pretending Windows will ever be a real OS for people with more than 100 IQ.

    • 1 month ago
      Anonymous

      >cmdlets default to "Continue" on error condition
      Exactly like bash unless you use "set -e"
      >there is Windows Powershell and Powershell (pwsh)
      Yes? And? They needed to uodate the core language and fix a bunch of shit that would break a lot of backward compat so they renamed the base executable from powershell.exe to pwsh.exe so that they could be installed sidebyside on the same OS. Would you rather have them call the new one powershell.exe too and have shit just not work because you never know what version its actually running?
      >Inconsistent Verb-Nouns, Sets that actually delete, etc.
      ????
      Are you talking about Set-Content?
      >exception machinery doesn't work unless you set some stupid variable to force cmdlets to "Stop" on error
      $ErrorActionPreference = "stop"
      # essentially equivalent to
      set -e
      >no built in parser for basic winshit like Ini files or even binaries found literally everywhere: .lnk shortcut files.
      Yea except there is a built in parser for csv, for xml and for json.
      If you want to parse .ini files you can write your own [regex] based switch statement in under 50 lines.
      Parsing the ini is made TRIVIAL by the fact that powershell supports full PCRE regular expressions everywhere OOTB.

      • 1 month ago
        Anonymous

        Anon that fool knows what he is doing.

        He conveniently skipped over full Json, CSV, XML, CliXML support and choose to nit pick on muuh Ini.

        Also -NoProfile eliminates long start ups, which is almost always due to morons bloating their ptofiles. On my machine pwsh boots up ~150ms after first time .NEET warm up.

        Powershell is infenitelly better than what is on *nix, face it morons we are the new NEETS.

        • 1 month ago
          Anonymous

          My powershell profile is literally 1500 lines long, and despite that it contributes 1/16th of the startup time of the posh-git module alone.
          If you use posh-git, beware that it is likely the reason for slow starts.

  6. 1 month ago
    Anonymous

    >literally perfect
    Yeah no.

    Bash:
    >Full compatibility with and native to Linux
    >Full compatibility with and native to BSD
    >Full compatibility with and native to MacOS
    >Full compatibility with and native to Haiku
    >Substantial compatibility with native support on Windows (via Cygwin or MSYS/2)

    PowerShell:
    >Full compatibility with and native to Windows
    >Middling compatibility with other operating systems (and only via .NET)

  7. 1 month ago
    Anonymous

    honestly, I'd try it on Linux if it weren't for the fact Fedora doesn't ship it, probably because it's some nonfree gayware covered in some veneer of "b-but the source code is here" much like how other shit like Google DartVM isn't available. If it isn't in Fedora, I assume it's botnet, doubly so if it isn't in Guix or if the nixpkgs source is basically, download tarball, fixup some ELF headers, frick off.

    • 1 month ago
      Anonymous

      Powershell is just, weird. It is both excellent because you can runtime link to any .NET assembly at any time and can even DLLImport kernel32, etc. It's kind of funny on Windows basically calling VB.NET code in Powershell or doing EnunWhatever functions and it's something that entirely mogs basically any "shell" out there.

      Overall I have mixed feelings. I'd say in 2024, all these things are shit and people should focus on UX usability on the terminal first and "scripting" dead last. Powershell, IMO, mogs the shit out of bash in virtually every respect and the .NET object system means you can usually do the more modern "API-y" interactions with web services and stuff. Azure has a Powershell module that's not that horrible to use on the terminal, compared to the azure-cli shitware before.
      On top of that, Powershell actually has a module system so including code is much much easier than anything bash offers.
      Only thing bash does better is being friendly to the baby ducks who can't use anything else and the fact that bash's pipelines "always" worked and it never tried shoving a bunch of weird broken incompatible aliases on everyone that every powershell user deletes in $PROFILE (Powershell). that and is probably true too.

  8. 1 month ago
    Anonymous

    fizzbuzz, go

    • 1 month ago
      Anonymous

      for ($i = 0; $i -le 50; $i += 1)
      {
      $o = "";
      if ($i % 3 -eq 0) { $o += "Fizz" };
      if ($i % 5 -eq 0) { $o += "Buzz" };
      if ($o -ne "") { echo $o } else { echo $i };
      }

    • 1 month ago
      Anonymous

      cnt=100
      for i in {1..$cnt}; do
      x=0
      (( i % 3 )) || {
      x=1
      print -n fizz
      }
      (( i % 5 )) || {
      x=1
      print -n buzz
      }
      if ! (( x )); then
      print $i
      else
      print --
      fi
      done

    • 1 month ago
      Anonymous

      1..100 |% {$x=""; If($_ %3 -eq 0){$x+="Fizz"}; If($_%5 -eq 0){$x+="Buzz"}; If($x -eq ""){write $_}else{write $x} }

  9. 1 month ago
    Anonymous

    >The perfect mix between scripting language and programming language. It's literally perfect. I use it for every single thing.
    reporting for duty, sir

    • 1 month ago
      Anonymous

      This.
      >powershell updates
      >ow oof my breaking changes
      >perl updates
      >use v5.30;

  10. 1 month ago
    Anonymous

    Wrong image

    • 1 month ago
      Anonymous

      >TFW know my dodekalogue like the back of my ass
      It truly is beautiful once you know.

    • 1 month ago
      Anonymous

      I'm still surprised this language gets updates. What does a tclsh even look like? I tried making one once, but it seems like a lot of work and no one else really did it.

  11. 1 month ago
    Anonymous

    use python, y'all goobers

  12. 1 month ago
    Anonymous

    but it's a shell

  13. 1 month ago
    Anonymous

    Anything with a good REPL beats this. Only thing Powershell has going on is the .NET ecosystem and cominh by default. F# blows this shit out of the water, isn't used more cause Microsoft is deliberately neglecting it.

    • 1 month ago
      Anonymous

      they ported all the useful features to c#

  14. 1 month ago
    Anonymous

    >I use it for every single thing.
    name 1 thing

    • 1 month ago
      Anonymous

      I won't name the obvious management of windows machines
      API testing

  15. 1 month ago
    Anonymous

    Can it help me to commit suicide?

    • 1 month ago
      responding to organic post

      >scripting languages
      >committing suicide
      weird association, don't you think?

    • 1 month ago
      Anonymous

      Permission denied.

  16. 1 month ago
    Anonymous

    That's Google ZX or, if you're zesty, Bun Shell.

  17. 1 month ago
    Anonymous

    I love powershell and I use it for everything nowaday, but it did take a long time of using it before it finally clicked.

    It's certainly not perfect, there are definitely a lot of little rough spots and weird gotchas but overall it's extremely based.

  18. 1 month ago
    Anonymous

    ITT: bash sunk cost morons coping

  19. 1 month ago
    Anonymous

    >can't even tab completion
    >the most moronic & unintuitive syntex imaginable
    >OOP homosexualry
    >shell language that is useless on the shell prompt
    nobody use this shitware unless they have too

    • 1 month ago
      Anonymous

      >can't even tab completion
      I hope this is a shitty troll. Powershells tab completion is 1000000000000000000000x better than bashes. It is provided by the PSReadLine module (which is built-in since windows 7). You can tab complete every cmdlet name, you can tab completely every -Parameter of every cmdlet. Hell, even your own scripts get free tab-completion support OOTB in powershell. You also can do ctrl+space to get a selectable menu of options to choose from, akin to how zsh works.

      Have you ever in your entire life had to write a bash-completion file for a bash script or utility that you wrote? It's pure insanity, not to mention it requires the user to "install" the tab completion support separately. In powershell you givw them your script and it #JustWorks
      >shell language that is useless on the shell prompt
      Ah yes, another person who has literally never used PowerShell enters the thread to criticize it.

      What is it about bash users that gets their panties in a twist when people like powershell?

      • 1 month ago
        Anonymous

        >It is provided by the PSReadLine module
        kek
        by default its doing sorting completion from A-Z or 0-9, accessing any binary or utility this way is fricking moronic.
        >Ah yes, another person who has literally never used PowerShell
        i use it from time to time and aside really simple operations its just not usable on the CLI, its designed badly for this purpose they should just add a standard python library for windows and everyone will be way happier.
        powershell is a disgusting failed product and this is why nobody use it outside the windows environment

        • 1 month ago
          Anonymous

          > is why nobody use it outside the windows environment
          Maybe that has more to do with the fact that it wasn't even available outside of Windows for the first 15 years of its life?
          People have literally decades of built-up inertia behind their bash script pipelines at this point, not easy for anything to break that.
          Hell, look at competitor shells like fish or zsh that are objectively more feature-filled and offer better UX than bash. They never caught on because they aren't the default, and never will be.
          > use it from time to time and aside really simple operations its just not usable on the CLI
          Why? I'll admit to you that I used to think this too, until I had to use it for work for months. It's painful to use when you don't know all the common object types, because you can't effectively use the pipe operator | without fricking things up. Pipelines in PS do not work the way you expect coming from a unix shell, and it really fricks with your head for awhile. Eventually you'll do it enough that you begin to memorize all the common object types emitted by each cmdlet and know their properties and suddenly everything becomes a million times easier and it just clicks.

          • 1 month ago
            Anonymous

            >fish or zsh
            these are literally bash interpreter with a different shell.
            >Maybe that has more to do with the fact that it wasn't even available outside of Windows for the first 15 years of its life?
            if it was as good as you describe, it will not be the reason not to use it.
            CMD was the dominant prompt interface for windows and everyone shift from it as soon as powershell came out, since its even worse
            >Why?
            because it's just not built for that, it's built to compress script lines into files.
            and in this case i don't see it as any real advantage over languages like python, the only advantage is that it is built in the system standard protocols, API, environment variables, binaries etc...
            so its just one of these software tools that you must use but its impossible to like

          • 1 month ago
            Anonymous

            >fish or zsh
            >these are literally bash interpreter with a different shell
            Lol no, Bash and Zsh have ton of subtle differences. What Zsh has is a POSIX and Ksh compatibility modes, but it doesn't always support all of Bash's extended features. Using Bashism for anything long standing is kind of a bad practice anyways. Better switch to a real programming language, or at least DON'T remove Bash so you can keep using it through a shebang if you need to.

            Fish is completely different from any of the previous shells, the manual pretty much tells so they don't aim to support POSIX behavior but be an interactive shell with its own scripting capacities.

  20. 1 month ago
    Anonymous

    Powershell helped me with a Fortinet Reporting issue recently. The reporting is dogshit and only XML reports were formatted properly with the data I needed, but obviously not great for presenation.

    Wrote a simple script with a foreach loop which imports the XML files and parses through them and assigns each value to a column in an array, then export to CSV which is easily readable in Google sheets table.

    Not a huge accomplishment but I'm in a more senior role and need to speak to management with raw data to properly size our firewall catalog based on the throughput of our current devices. Small, medium, large, etc.

    • 1 month ago
      Anonymous

      But you could have made a bash script which calls out to sed and awk to do that

    • 1 month ago
      Anonymous

      This is the kind of shit powershell does very well. Perfect use case for it.

      But you could have made a bash script which calls out to sed and awk to do that

      Yeah jackass, try parsing XML with bash then talk to me again and we'll see how little sanity you have left.

  21. 1 month ago
    Anonymous

    its alright

  22. 1 month ago
    Anonymous

    real neet hours

Your email address will not be published. Required fields are marked *