I'm writing a powershell script at the moment. Why did I chose it? I didn't - it's the only thing guaranteed to be on Windows (realistically). The problem with

I'm writing a powershell script at the moment. Why did I chose it? I didn't - it's the only thing guaranteed to be on Windows (realistically). The problem with powershell as a scripting language, is it's designed to also be used as a shell. Which means, literals can be strings, function parameters are not separated, etc. It reminds me of Tcl in the 90s. I really like what the powershell environment provides (like cmdlets, .NET) - but the language itself is dismal. I would have preferred to have seen an existing scripting language, with .NET bindings added to it... the "NIH syndrome".