Why do TUI developers insist on doing such weird stuff when they could just make a GUI
Because making a decent GUI is harder than making a decent TUI. Also TUIs give you some nice things for free like working over SSH easily, but I suspect the lower dev effort is the big thing.
Presumably preference of their users. From what I know, other than for cursor, the GUI interfaces are less popular than the TUI ones. Personally I also did not expect that I would really like the TUI experience, but it's hard for me to switch away from it now because it has become so central to my workflow.
It's easier to ship a TUI app cross-platform, the constraints around UI and state are often simpler, and some good libraries/frameworks (e.g. [1][2]) exist to make a modern-looking UX.<p>[1]: <a href="https://github.com/charmbracelet/bubbletea" rel="nofollow">https://github.com/charmbracelet/bubbletea</a><p>[2]: <a href="https://github.com/Textualize/textual" rel="nofollow">https://github.com/Textualize/textual</a>
I considered a GUI for a small Python project of mine, but couldn't find anything quick, simple, and portable. I ended up opting for a TUI with a few ASCII art boxes.
[flagged]