News for hackers. Stuff that matters.
Re:Text Processing in the Shell by throwaway_pdp09 on Tuesday March 17, 2020 @04:37AM (#22602927)
I find these posts annoying that say we're anchored in past tech and we must be able to do better, but never suggest how.

Please make a suggestion or two.

(NB ultimately our character handling is based on 'writing' which goes back thousands of years, not 50, and it survives well).

Re:Text Processing in the Shell by JdeBP on Tuesday March 17, 2020 @07:42AM (#22603878)
I suggest learning from history. The doing better has already happened. The 1960s terminal I/O model evolved into the console I/O model during the 1980s; from firmware-mediated access to CGA, through the VIO+KBD+MOU subsystems of OS/2, to Windows NT console objects.

* http://jdebp.uk./FGA/tui-console-and-terminal-paradigms.html

* https://news.ycombinator.com/item?id=17238350

Re:Text Processing in the Shell by throwaway_pdp09 on Wednesday March 18, 2020 @04:58AM (#22614781)
That seems to have nothing to do with text processing, only screen addressability.
Re:Text Processing in the Shell by JdeBP on Wednesday March 18, 2020 @09:26AM (#22616363)
If you actually read the whole discussion to this point, you'll see that the discussion started with being constrained to the models of teleprinters, not text processing.
Re:Text Processing in the Shell by zokier on Tuesday March 17, 2020 @06:11AM (#22603421)
Structured data and tools that operate on that structure. Maybe steal a thing or two from LISP machines. I remember the one time I had to work on an AS/400 (iirc) how interesting it was that one of the fundamental building blocks were records instead of dumb files. PowerShell has interesting ideas too, but it'd need to be far more built-in and integrated to the OS to truly shine.