4 ms·
You're not supposed to write very advanced TUIs (advanced being subjective here). It's not what the interfaces were designed for. The interfaces for advanced U
by arghwhat 5y ago
You're not supposed to write very advanced TUIs (advanced being subjective here). It's not what the interfaces were designed for.
The interfaces for advanced UIs is Wayland and X. TUIs are meant for compatibility, not fancy ability.
- kelnos 5y agoRight. And on top of that, one of the useful benefits of a TUI is that you can use them while ssh'd into a remote server. If your fancy TUI is expecting to get raw access to the keyboard, it's not going to work in a ssh session.
- _jal 5y agoWho says? Actual question. > TUIs are meant for compatibility Nonsense. Our machines don't even get GUIs installed.
- arghwhat 5y agoThat's exactly what the compatibility is for. Tools that work in the absence of anything advanced, with nothing but a few escape codes to "draw". Otherwise it wouldn't work on the kernel console (the only thing available without a GUI installed), over SSH, over serial links, even still on dedicated terminals and teletypes.
- _jal 5y agoTerminal is still a first-class UI mode, not some fallback. If some tooling doesn't work for us (which means over a terminal), then we don't consider it. If something doesn't expose functionality over a terminal, that functionality doesn't exist.
- arghwhat 5y agoSure, it's a first class UI mode from the 70's, which is extremely useful. Any development of it would be in direct conflict with its qualities. > If some tooling doesn't work for us (which means over a terminal), then we don't consider it. Who is "we"? Even the most die-hard TUI fan uses them through a GUI terminal emulator, making that argument fall entirely apart.