this post was submitted on 11 Nov 2025
75 points (100.0% liked)
Programmer Humor
39058 readers
162 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The thing I never understood about PowerShell is that it's partially more verbose than C#, which is one of the most verbose programming languages in existence. It just feels like you might as well go for a full-fledged programming language at that point.
The appeal of Bash et al is that the scripting is almost the same as the interactive usage, which you already know. But because PowerShell is so verbose, I'm really not sure people do use it interactively.
I guess, that code snippet in the article makes somewhat of a difference, in that PowerShell offers better features for interop between processes. But man, that still feels like it could've been a library instead...
Powershell is nice for scripting things close to the (windows) OS. But (granted I'm not exactly some PS wizard, I've just used it a few times for minor things at work) I agree it often feels unnecessarily verbose and cumbersome. For example the fact that you need to define a whole function to alias even just a single command with parameters. And just overall I find it very hard to read (though maybe that's on the guy that did the powershell stuff before me, I don't have great sample size here).
But I'll take what I can get.
PowerShell is fantastic in practice but whenever I think of writing shell scripts I think of bash first.
Bash is a lot more pleasant to work with overall, the biggest concern most people have is that it can be cryptic. IMO PowerShell scripts can be the exact same kind of voodoo.