> With Bash you get a wealth of tools because everything can handle text.
... and all those tools work seamlessly in Powershell, too. .NET objects are passed around within Powershell, but traditional dumb text is used for out-of-proc stuff. Where is the "fatal flaw?"
I don't understand where the perceived downside is - you wish Powershell was implemented in Python, not .NET?
The fatal flaw is that I have to distinguish between "within Powershell" and "out-of-proc". I simply don't have this issue with plain text; I don't know or care what language/runtime the programs I use are written in/for because they all use the same interface.
... and all those tools work seamlessly in Powershell, too. .NET objects are passed around within Powershell, but traditional dumb text is used for out-of-proc stuff. Where is the "fatal flaw?"
I don't understand where the perceived downside is - you wish Powershell was implemented in Python, not .NET?