Text is an extremely information dense medium. It makes sense for user interfaces to be centered around text. This keeps the focus on the data and its transformation.
Stop Making TUIs
311–320 of 579 posts
Re: Stop Making TUIs
#312Earlier quoted context omitted.
TUIs are not CLI programs though. They're GUIs which render in a terminal
The shell's line editor is a TUI. It's a simple text editor embedded right there in the command line. It can even render your shell history by pressing the arrow keys.
Sure yes. A terminal is a GUI. But it's a GUI used to both run cli programs (which can be piped etc) and TUIs (which cannot)
Re: Stop Making TUIs
#313Re: Stop Making TUIs
#314No
Re: Stop Making TUIs
#315Another trend is to bring graphical features into terminal emulators thanks to the initial protocol and implementation work in Kitty with the Kitty Graphics Protocol.
https://sw.kovidgoyal.net/kitty/graphics-protocol/
And now libghostty has caught up with a full implementation of the protocol in a second terminal emulator. I guess that mitchellh has plans for use in Superlogical... https://hachyderm.io/@mitchellh/117135178412268410
Re: Stop Making TUIs
#316Counter proposal: stop making gui, ONLY make TUI.
+ seamless cli integration + network portable + graphics (!!) with modern emulators + always themable + scriptable + works with any navigation modality + you can copy & paste entire segments of your window easily + easy to consistently theme + did i mention entirely network/os transparent? + blazing fast
tongue-in-cheeck mostly, but i assure tfa, the tui serves useful functions. i spend >80% of my time in terminal, and having a pane to do some task a gui would otherwise be needed for is a sheer blessing. being able to essentially move my session to a laptop is wonderful. no mucking with screen sizes or weird X11 wonkery (if you still use x11). what would blow my socks clean off is a tui/gui+gui/tui backend pair so we can have our tui and you can gui it tooie.
Re: Stop Making TUIs
#317Sorry, no.
I don't want to forward a whole desktop environment just because I want to use a small application I have written for myself.
TUIs are much more portable, easier on eyes, can be information dense, and resistant to lassiez-faire UI library changes on platforms. They don't need GPUs to render, megabytes of RAM to run, great amounts of bandwidth to access from afar.
I'll write a library for the functionality, and will slap a TUI on top. You want a GUI, write it yourself. Everything is GPLv3 licensed. You can do whatever you want as long as you respect the license.
Re: Stop Making TUIs
#318Counter proposal: stop making gui, ONLY make TUI. + seamless cli integration + network portable + graphics (!!) with modern emulators + always themable + scriptable + works with any navigation modality + you can copy & paste entire segments of your window easily + easy to consistently theme + did i mention entirely network/os transparent? + blazing fast tongue-in-cheeck mostly, but i assure tfa, the tui serves useful…
Emacs does that.
If you run an emacs server you can connect to it with an emacs in TTY and one in GUI mode.
Re: Stop Making TUIs
#319Re: Stop Making TUIs
#320Counter proposal: stop making gui, ONLY make TUI. + seamless cli integration + network portable + graphics (!!) with modern emulators + always themable + scriptable + works with any navigation modality + you can copy & paste entire segments of your window easily + easy to consistently theme + did i mention entirely network/os transparent? + blazing fast tongue-in-cheeck mostly, but i assure tfa, the tui serves useful…
Emacs does that. If you run an emacs server you can connect to it with an emacs in TTY and one in GUI mode.
Emacs does everything. I want everything to be more like Emacs