The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I started using Visual Code for my Unity game development, and noticed that it also can be used as a terminal\editor for PowerShell scripts, etc. It appears that it has some nice features too, for this. Worth a look I think.
The one (huge) benefit of PowerShell over Bash (IMNSHO): You're working with actual objects, with properties and methods, rather than just parsing strings. Just about anything in .NET that's public can be invoked.
As for your longer rant (elsewhere in this thread): Are you aware of WSL? It's not merely a VM or a re-implementation of existing commands like Cygwin.
A few years ago I started poking around one of my DLLs with PowerShell, just for the fun of it, and started scripting some things using some of my classes that were never meant to be scripted / for scripting.
Some "feature" I wrote with PS became something a customer wanted us to implement, but management saw little very value in us implementing it right in the program - so the customer got it as a PS script.
They often have really nice offers. Sometimes a bit old stuff, but still good
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.