So you blame bad developers for stuff ? Amazing. > The provisioning takes 2 to 3 hours. After 2 hours the script would abruptly quit because of some syntax er

So you blame bad developers for stuff ? Amazing. > The provisioning takes 2 to 3 hours. After 2 hours the script would abruptly quit because of some syntax error. 2 hours wasted Anybody who designed such thing is bad. If stuff fail after 2 hours, you should be able to repeat it in idempotent way to just continue or you skip sections with parameters. Your syntax error problem is the same in any other shell, and in all dynamic languages. > A lot of Microsoft plugins have PowerShell plugins. This is what makes PowerShell valuable, not some attribute of PowerShell itself. Nonsense. I almost never use any of the "plugins". PowerShell on its own is game changer. Like the first dude already said, I have yet to see a problem that can't be done in 2-5 lines of code that is joy to read even in shorthand form, unlike countless magic chars, something that is known to be bad pattern in OOP. > Really what Microsoft should have done is to make those plugins available to C#. That is really NOT what Microsoft should have done instead of PowerShell, maybe alongside it. But since you have PowerShell, you don't need it that much. Besides, it already exists for almost decade. > Then any syntax errors in the script can be caught ahead of time, instead of after 2 hours of running. You can do this today.