Programming

It's newer and Microsoft based. Easy way to get a bunch of people on the hate train for those reasons alone.

PS was built from the ground up to be intuitive. There are some interesting videos from the MS devs talking about the design process.

I can see how PS might be better for writing actual programs in but the wordiness really gets in the way when youre just trying to write something on the command line so it feels poorly optimized for cli usage. Bash is very poorly optimized for writing programs otoh.

My main issue with PS is that it is JavaScripty. And by that I mean, it makes tons of assumptions on what I "mean" by my command. And it's usually right and thus I don't see any issues. But when those assumptions are wrong, I have to do all kinds of parameter fuckery to make it be what I "expect".

None of that is true is bash. It doesn't make many assumptions at all (at least none that I've come across). Things act the same when I'm using bash in a script vs the cli vs over an ssh connection vs within a subshell, etc.

And ya the whole "it's pretty verbose" is irritating too (though that could also be a counter argument against bash relying on magic variables and abusing the shit out of symbols).

I don't hate PS but I don't enjoy spending time in it. I don't hate bash but it hurts me less when I use it

It's not necessarily PS itself, I bet it would be fine on a Linux machine with a typical Linux terminal. It's just that I cannot stand the rest of Windows, especially the CLI part, especially cmd: Awful to no tab complete support, no command history across cmd restarts, if tab complete works its only for files and even sucks there because of the ignore case design and completing a full name instead of to the next clear step (eg. "tes" for a dir containing "test.exe" and "test.mp4" will complete to "test.exe" instead of "test."). Additionally, I associate PS with Windows and tasks on it. Most things I want to run on Linux only I write in C/C++ (depending on the task itself ofc). If I want compatibility with Linux and Windows I use python. To install that script to a usable state it's literally a single command on Linux, if the method of transferring the script (probably a git repo) supports saving the executable permission bit: sudo cp script.py /usr/local/bin/patchjar.py. Even if you want an own directory with your own path, that's no problem: Just cp a .sh file to /etc/profile.d/ that appends to the path. And removing it is as easy as deleting that file. On Windows? Chocolatey has a ~100 line script just for that purpose, backs up the path just in case and even explicitly states uninstall it can break your whole system? Why? Because Windows uses a single global PATH variable for everything. You need to edit the registry, extract your path with loops, remove it and write it back. And that's a pattern being repeated through the whole OS. You want to move a window on the screen or start something on another monitor? Well fuck you. On Linux? assign [app_id=TuxKart] workspace gaming. For an OS claiming to be integrated with everything in itself that seems like pretty damn dumb and frustrating to a dev.

I have done a lot of powershell scripting and found some very annoying edge cases, they all have solutions, but feels unnecessary. I once had a issue, where I had a dynamic array of strings and if thst array was only 1 long it would give you the first character instead of the first string. I don't know exactly what made that happen, but I think it had something to do with functions or classes.

The object model is much easier to understand in PowerShell.

If you are writing a long enough bash script that the readability is an issue then you should be looking to introduce a more specialized tool, like Make, or a more readable one like Python, into your project

Bash is specifically designed to be glue not the whole thing