2 ms·

I was extremely well versed in PowerShell early into its development. It was indispensable when it came out. VBscript and Cygwin were the only options; both of

by nunez 2y ago

I was extremely well versed in PowerShell early into its development. It was indispensable when it came out. VBscript and Cygwin were the only options; both of them sucked. The ability to use native .NET objects in scripts was insane; I definitely abused that! Nowadays, Git Bash and WSL2 replace a lot of the value that PowerShell provided. It's purpose was to drive Microsoft away from the GUI, and, at that, it more than succeeded.

oblio 2y ago
> VBscript and Cygwin were the only options; both of them sucked. I'd challenge the Cygwin aspect. With judicious use of cygpath & co., you can go VERY far with Cygwin. I've built an entire SaaS deployment system on top of it (and Python).