3 ms·

can either of you elaborate what you mean? are you talking about support for structured data passing between scripts/programs?

• bombcar 6mo ago
  Yes - https://devblogs.microsoft.com/scripting/working-with-json-data-in-powershell/?hide_banner=true https://devblogs.microsoft.com/scripting/working-with-json-d... Tons of bugs in scripting in Unix come from the fact that data and metadata are interspersed in the same stream (you can mitigate somewhat with stderr vs stdout but hardly anyone does). Examples include things like trying to handle random filenames from * expansions. It’s a bit more annoying to deal with sometimes, but for actual scripts it’s much more foolproof. xargs is one of the programs that is designed to work around the original issue.
  • em-bee 6mo ago
    i agree. you may enjoy these recent comments about better terminals: https://news.ycombinator.com/item?id=47812724 https://news.ycombinator.com/item?id=47812724 https://news.ycombinator.com/item?id=47811986 https://news.ycombinator.com/item?id=47811986 https://news.ycombinator.com/item?id=47807195 https://news.ycombinator.com/item?id=47807195
• Avamander 6mo ago
  Yes, structured data between scripts and programs. No xargs, tee, awk, sed, grep mangling. No "argument list too long" errors. So many problems are avoided, but at the same time the Windows ecosystem is just so far from providing an properly usable terminal experience. Things are still really not designed to be used from PowerShell.
  • em-bee 6mo ago
    right, see my response to the sibling comment.