News for hackers. Stuff that matters.

A comment on Terminal escape sequences in Git commit email field. Parent comment

Re:Terminal escape sequences in Git commit email field by enriquto on Monday March 29, 2021 @01:12AM (#26617916)
> When I type "ls", I'm getting a text-serialized list of objects. Why can't I just get the (serializable) list directly?

Because then the output of ls can be used by programs that don't know what a list is, or what a file is; and this is breathtakingly beautiful.

[ Parent | on HN ]
Re:Terminal escape sequences in Git commit email field by Scene_Cast2 on Monday March 29, 2021 @01:13AM (#26617919)
Make it auto-serialize to text if the receiving end doesn't understand lists. Working with text directly doesn't get me any type safety, or any safety at all (unless I'm writing a one-off, where it matters less).
[ Parent | on HN ]
Re:Terminal escape sequences in Git commit email field by enriquto on Monday March 29, 2021 @01:21AM (#26617955)
"type safety" is the "structured programming" of the twenties
[ Parent | on HN ]
Re:Terminal escape sequences in Git commit email field by comex on Monday March 29, 2021 @01:57AM (#26618120)
...As in, it will become so universal that languages without it are utterly unheard of, except for assembly and joke languages?
[ Parent | on HN ]
Re:Terminal escape sequences in Git commit email field by Too on Monday March 29, 2021 @03:34PM (#26627099)
Ok cool I can pipe ls into gz and pipe further into scp. Now what? How do I use it on the receiving end after unzipping it again? You still have to parse it into a structural list of files over there somehow to make use of it? Not everything is a tunnel.

Structural data can still be serialized easily, take json for example which’s spec fit on a napkin.

[ Parent | on HN ]