Re: Have you used Powershell?
"How many of the Bash people who are on here bashing Powershell have actually used it?"
I tried it once or twice under windows, and like the Eldritch Abomination that is ".Not", it's hellspawn 'powershell' is the hideous nightmare from the bowels of hell that it's portrayed to be by us "bashers".
When I decided to learn Linux and BSD, I had to start over with the shell. In the case of BSD, there are actually TWO shell syntaxes that are slightly different (csh vs sh/bash). I find that once I dove in, it was relatively easy to pick up and very very logical, and it helped me to learn Perl.
Powershell, on the other hand, is _SO_ tied into the ".Not" thing that I couldn't stomach it for more than a few minutes. It was like: no. no. NO. NO! NO NO NO! NO NO NO NO NO NO NO!!! I was like Saavedro in that pathetic 'No' scene towards the end of Myst: Exile.
".Not" was the cancer that really killed windows. It increased the slowness, tried to turn senior developers (used to WinAPI, MFC) into JUNIOR developers (by changing the game and all of the rules into bass-ackwards "object-oriented" nonsense that's really BLOATED and INEFFICIENT collection-based sewage). No thanks. re-learning "that" simply because it's *new* is not acceptable. On the other hand, learning bash after using CMD and command.com was kinda interesting.
FYI - I'd written a command line shell for Windows 3.x back in the day, extending the DOS commands and allowing you to run windows applications either synchronously OR asynchronously, with some rather nice extensions. There was also a REXX for windows, which my shell played nice with (by request, actually, I made those modifications). But of course Win '9x made it all MOOT with CMD playing nicer with windows applications and the 'start' command (not the same as the start button). But if I'd had cygwin back then, I would have used THAT instead.