The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Fridge? Ha! If we wanted something kept cool, it was put on the kitchen outside windowsill. (During the summer, we didn't buy stuff that needed to be kept cool; milk was delivered in the morning and was warm by lunchtime.) We did have a fridge, but it didn't work so we just used it as a cupboard. So: "a fridge? You were lucky; there were a hundred and sixty of us living in a small shoebox in the middle of the road."
same here, I keep trying to learn it but it just doesn't seem to sink in properly. I did manage to create a small script recently when moving from VS2017 to VS2019, which upgraded all my C++ projects, and tidied up the rest. If only I could expand on what I learned.
I dare to claim, it's a simple matter of getting used to.
You can use .NET objects from PS though. I did this a while ago until MS coughed up Extract-Archive to unzip stuff via System.IO.Compression in a PS script. Not exactly C#, but you still have to learn less new stuff.
Actually, it's the exact opposite of cludgy. All commands follow the same pattern: verb-noun. The parameters all follow the same pattern: -parameter (with maybe additional switches). It really looks like it's a matter of getting used to for you. PS' syntax is pretty different from CMD's syntax, bash's syntax, C#'s syntax, Delphi's syntax (I'm starting to run out of syntaxes I'm really used to here).
PS is, in fact, absolutely self-consistent though.
It's a little like a French car - internally consistent and makes sense if you've never seen another car. Confusingly different for no apparent reason if you compare it to almost anything else. It's almost as if the design criteria was to make it different from everything else.
I spent ages doing the same automation in Python because it was easier and more functional, until I got a job where the locked down environment forced me to use Powershell.
Now I'm nervous about a tool that's installed by default, and which anyone could use.
I disagree with "never seen another car". You're still claiming it's objectively worse. The thing is, I know exactly how you feel! Heck, my muscle memory makes me sometimes work faster when I shell down to CMD and do something there. I know how you feel!
It's just that PS isn't objectively worse, like your french car. It's very different, but it's cool. By now, it's clear that you haven't attempted giving PS a chance. You haven't built complex pipes in Bash & PS (well, you may have in Bash but you surely haven't in PS). You haven't tried reading complex PS scripts.
All that different stuff serves a purpose, it helps getting things done! It's not only internally consistent, it's very logical once you give it a chance. Which you don't.
Speaking of which, why aren't you worried about CMD? It's installed by default, anyone can use it and you sure as hell can, with some effort, do really complex stuff there. Why aren't you worried about VBS? It's ability to call C-like APIs is limited (read: non-existant), but a heap ton of Windows is accessible through COM thus through VBS (well, technically, a COM-object isn't VBS-callable by default, it needs to support IDispatch while COM only requires IUnknown, but MS are pretty good at supporting administration through VBS). Speaking of administration, WMI is installed by default as well.
But it's only PS that worries you. Of course.
PS: at the beginning of this discussion, C# was mentioned. Now it's Python. The thing is, C# is, syntactically, way more similar to PS than it is to Python. This isn't an objective discussion, isn't it?