←back to thread

Things I've learned building a modern TUI Framework (2022)

(www.textualize.io)
331 points willm | 3 comments | 11 Aug 24 12:22 UTC | HN request time: 0.21s | source
Show context
mikkelam ◴[11 Aug 24 16:47 UTC] No.41217448[source]▶
Why do software engineers care so much about TUI? I really don't get it. I love a good command line program. But TUI just doesn't appeal to me.
replies(9): >>41217465 #>>41217542 #>>41218233 #>>41218568 #>>41219439 #>>41220309 #>>41221102 #>>41222105 #>>41223080 #
squigz ◴[12 Aug 24 04:08 UTC] No.41221102[source]▶
Because I don't need a resource-heavy GUI for something as simple as a music player.
replies(1): >>41221748 #
1. zokier ◴[12 Aug 24 06:45 UTC] No.41221748[source]▶
GUI is not intrinsically any more resource-heavy than TUI; ultimately you need to render stuff on screen somehow and get user input, and going through tty layer just is extra bloat.
replies(2): >>41222519 #>>41223635 #
2. creesch ◴[12 Aug 24 09:00 UTC] No.41222519[source]▶
It isn't extra bloat when you are already using that layer for other things and also doesn't require any extra packages or connections on your side of things.

Specifically when dealing with remote environments where you connect to through ssh anyway it is really awesome when some things can be done through a nice TUI. In that context a GUI would actually be more resource heavy considering that it likely will be web based with much more client side processing happening for the GUI.

3. squigz ◴[12 Aug 24 12:29 UTC] No.41223635[source]▶
> GUI is not intrinsically any more resource-heavy than TUI

Okay well, maybe you should tell that to the GUI developers :P