[openrisk]

There is something intriguing and (maybe telling) in the longevity of the terminal mode.

It was invented out of pure necessity when various resources (compute, screen, network etc) were really scarce. So it is extremely information dense. No superfluous eye candy, just the Word.

In a sense the terminal is now the most respecting of our own limitations when parsing the firehose of information that is drenching every screen.

What is missing though (after all those decades) are any widely adopted conventions for how to structure anything more complex than a simple top-to-bottom text flow.

Once you move past the static page paradigm the possibilities are endless and that is not always helpful. But for a range of typical current use cases that involve information firehoses (a mailbox, an rss reader, a social media app, a wiki etc) it would be fantastic to develop common TUI design principles.

[amelius]

I personally want terminals to look more like fast Jupyter notebooks.

[openrisk]

I am rooting more for the htop aesthetic

[ykonstant]

One day; one day some enlightened soul will write a Command Line Application (as opposed to a terminal emulator) allowing all the goodies of the DOS command line and its frame buffer with none of the downsides; then we will not need curses/ncurses/etc anymore but a simple and sane drawing context unchained from the terminal protocols.

We can then easily write beautiful TUIs for the command line, with easy and ergonomic random screen access and all the nice things, and leave the terminal for actual terminal operations.

[amelius]

How would you take advantage of a gpu?

[nurettin]

You mean like Org Mode?