3 ms·
I was excited about PowerShell at first but after doing a mid size project it, I don't like it anymore. It's such an odd language with too many quirks once you
by rqtwteye 2y ago
I was excited about PowerShell at first but after doing a mid size project it, I don't like it anymore. It's such an odd language with too many quirks once you get serious. I think they would have been better off using C# syntax.
- deleted 2y ago[deleted]
- hobs 2y agoThe syntax is barely the problem, the weird console rendering of objects behavior, the mixed object/text representation (since not everything buys into the objects), the breaking changes in the cross platform posh, the poor library support and requiring to load the world on importing modules... there's a lot of stuff powershell got wrong enough to avoid anything with it, and I have done plenty of serious things with it :)
- patmorgan23 2y agoBecause PowerShell is a shell interface/scripting language. That's like complaining it was difficult to build a project using bash or CMD. It's great to system administration, having named attributes + pipelining is awesome compared to bash/CMD
- rqtwteye 2y agoBeing a shell interface/scripting language is no excuse for making a bad language.
- mystified5016 2y agoI mean, there's really no justification for the Get-Help cmdlet. The -h flag has been universal for decades. If it were a replacement for 'man' it would be defensible, but not when most programs do not acknowledge -h