News for hackers. Stuff that matters.

A comment on Cicada – Unix shell written in Rust. Parent comment

Re:Cicada – Unix shell written in Rust by ori_b on Saturday July 01, 2017 @03:29AM (#14675887)
> what a more modern shell might look to address some of the problems of its predecessors like pipes that are essentially text-only, poor composability (see `cut` or `xargs`)

A new system and set of utilities. None of the Unix environment works in that world, and shoehorning it in would feel incredibly clunky.

[ Parent | on HN ]
Re:Cicada – Unix shell written in Rust by panic on Saturday July 01, 2017 @03:38AM (#14675912)
If you use bytes that are invalid in UTF-8 (e.g. 0xF5-0xFF) as delimiters / structure characters, you can use text-only tools to do structured operations on UTF-8 strings without ever having to escape anything -- the structural "characters" you would need to escape can never appear in the encoded bytes.
[ Parent | on HN ]
Re:Cicada – Unix shell written in Rust by carussell on Saturday July 01, 2017 @11:55AM (#14677598)
> If you use bytes that are invalid in UTF-8 (e.g. 0xF5-0xFF) as delimiters / structure characters

No need for that. UTF-8 is a superset of ASCII, and ASCII already includes a handful of control codes that could be used here.

[ Parent | on HN ]
Re:Cicada – Unix shell written in Rust by ori_b on Saturday July 01, 2017 @03:59AM (#14675956)
The Unix shell operates on binary streams, not on text.
[ Parent | on HN ]
Re:Cicada – Unix shell written in Rust by panic on Saturday July 01, 2017 @05:26AM (#14676234)
Ah, I thought this was about structured text (like JSON) vs. plain text -- binary content is a bigger issue!
[ Parent | on HN ]
Re:Cicada – Unix shell written in Rust by ori_b on Saturday July 01, 2017 @07:58AM (#14676709)
If you want to replace the shell with a structured one, the change needs to be pervasive, down to replacing the typical file formats, imo.
[ Parent | on HN ]