> why does posix sh deserve to win? It's plaintext pipes approach is really frustrating in 2016.
I think that in many aspects plaintext has won. Many historical records of the last century will be or have already been lost, because of formats that nobody can read.
OTOH, plaintext is readable and supported by almost everything under the sun.
I think it is weird that people say "plaintext has won" when basically every data format under the sun is structured, no one keeps data unencrypted, and transport protocols have basically grabbed all the mindshare as storage protocols.
But keep in mind I think it is bad for pipes only.
I have no problems with powershell wanting to pipe "objects"
but I still want a POSIX environment under Windows.
And about why POSIX deserve to win ?
For me it's about cross-platform command-line, I need to be able to run command-line tools that just behave the same under Windows, Mac OS X and Linux.
So far, Windows has ignored the command-line for years, and when they don't ignore it they change it every couple of years, from scripting hosts WSH to PowerShell to whatever else ...
Just sayin' it's hard to take Windows seriously when it come to the command-line environment, it is a huge mess.
> For me it's about cross-platform command-line, I need to be able to run command-line tools that just behave the same under Windows, Mac OS X and Linux
Then join my headache world of all 3 versions of bash doing subtly different things. We used to think our automation/deploy scripting could be cross platform if we used bash. Oh what heady and foolish days those were.
The value of this is that it works easily, portably, and with minimal overhead.
By bigger question is, why does posix sh deserve to win? It's plaintext pipes approach is really frustrating in 2016.