3 ms·
This can work with something like nushell, but obviously breaks the entire current universe of coreutils. In the normal world we can solve this problem without
by lordgroff 5y ago
This can work with something like nushell, but obviously breaks the entire current universe of coreutils.
In the normal world we can solve this problem without breaking everything by adding --jsonout or similar to all the coreutils and then we can have sanity by piping to jq.
- epse 5y agoNot necessarily though, as filenames aren't required to be valid strings, so that would break json syntax. And json doesn't have a syntax for "just a blob of bytes", besides the fact that wrapping bytes in text just to be decoded back to bytes seems silly to me, but that's an opinion
- deleted 5y ago[deleted]
- AnIdiotOnTheNet 5y ago> This can work with something like nushell, but obviously breaks the entire current universe of coreutils Good, because these utilities suck. Half of them only exists because the data is unstructured in the first place, the other half are mostly made of parameters that only exist for the same reason, and most of their names have no apparent relation to what they do. It is time to move out of the 1970s.
- ilyash 5y agoHi. Author of Next Generation Shell here. Totally agree. Also UI of the shell is stuck and ignores pretty much everything that happened in last decades. Here is my plan for the UI: https://github.com/ngs-lang/ngs/wiki/UI-Design https://github.com/ngs-lang/ngs/wiki/UI-Design Edit: but I do try to keep interoperability with existing bullshit.