3 ms·
Apart from shells having wacky syntax and semantics, due to shell pipelines being plain text, you spend a lot of time writing flaky mini parsers with stuff like
by jabl 10y ago
Apart from shells having wacky syntax and semantics, due to shell pipelines being plain text, you spend a lot of time writing flaky mini parsers with stuff like sed/cut/awk/perl one-liners/ to get the data you want.
In an alternative universe it would be nice if all these tools would consume and emit s-exprs. Or maybe I'm just wishing for the return of the Lisp machines, where AFAIK "the shell" was the Lisp REPL (never used one myself so I could be all wrong, of course).
Kids these days would of course use json instead, at least until the serious (tm) enterprise people would swoop in and replace it all with xml and ShellReplFactoryInstanceFactoryFactoryBean.
- daxelrod 10y agoAre you aware of PowerShell? Pipelines act on full .Net objects.
- catdog 10y agoThat ties it into the .Net ecosystem. Better to pass strictly data and not behavior but in a more structured way. Yet it should still be pretty simple so sth. like json would be the right direction to go.
- vram22 10y ago>ShellReplFactoryInstanceFactoryFactoryBean You forgot to include Adapter, Builder, Strategy and a few other words in that.
- vram22 10y ago>Kids these days would of course use json instead JSON? How last week. The cool(est of the cool) kids are already moving on to TOML and its ilk.