3 ms·

Didn’t PowerShell on Windows try this and basically failed? Well some people really like PowerShell but I didn’t see the concepts move over to UNIX side

• crabbone 4y ago
  One of the reasons why PoverShell approach cannot succeed now is that the system interface produces exit codes and unstructured text output. So, no matter how hard PoverShell tries to pretend that there's structure or that there's anything but strings and exit codes, it's all fake, and it starts breaking up very quickly, especially if you are used to work with programs whose interface is just that: exit codes and unstructured / randomly / uniquely structured output. Had the system offered programs an interface for outputting structured information, had it worked better at standardizing and unifying the way programs process structured input... PoverShell as a concept would have more ground to stand on. Right now, in the UNIX world, it is an even worse option than Python. So, there's no motivation to accept it. At least I haven't met a single system programmer who would have wanted to have PowerShell on UNIX. Only people who do that are Windows users who have some prior experience and who simply don't know much about the system they have for whatever reason ended up using.