71–80 of 304 posts
This is going to end up with TUIs that resemble old BBS ANSI art, such as https://16colo.rs/ It completely misses the reason people like current TUIs.
A UI design tool for TUIs -- made with Electron?... fun times!
Just `bun run dev`
This is nonsensical, there is nothing textual about the UIs being shown here. It doesn't stop being a GUI if you have a 1:1 representation of the concept within character cells. The UX actually matters, and TUIs are generally built for effectiveness and power (lazygit being an excellent example). But once you start adding mouse clickable tabs, buttons, checkboxes etc. you left the UX for TUIs behind and applied the U…
Well, except:
> a 1:1 representation of the concept within character cells.
TUI is build from text, and living within its constraints and what it's engine (usually the terminal) allows. GUI is build from graphics, and has basically a pixel perfect control of its own. This is a very notable difference, especially at the time when these terms were coined.
> TUIs are generally built for effectiveness and power
No, this is a result of different architectures and their constraints.
> But once you start adding mouse clickable tabs, buttons, checkboxes etc. you
TUI and mouse are predating the GUI (more or less). We had them already 40-50 years ago at the dawn of interfaces. We are now just moving back to them for practical reasons.
Am I the only one who thinks the recent TUI explosion is absolutely not necessary? I mean yes, code editor are great for this but a lot of the TUIs I see are so slow it begs the question why they exist to begin. CLIs are supposed to be remixable and scriptable. I think a better architecture would be to generally keep CLIs work like CLIs and have separate processes that add terminal rendering functionalities for those…
Am I the only one who thinks the recent TUI explosion is absolutely not necessary? I mean yes, code editor are great for this but a lot of the TUIs I see are so slow it begs the question why they exist to begin. CLIs are supposed to be remixable and scriptable. I think a better architecture would be to generally keep CLIs work like CLIs and have separate processes that add terminal rendering functionalities for those…
A UI design tool for TUIs -- made with Electron?... fun times!
Earlier quoted context omitted.
One justification for TUIs is remote access over SSH.
You can tunnel a port over SSH and get a web UI locally, though it's not commonly done. I feel like more people would actually do this if tunneling a port was just ever so slightly easier (like, you're already SSH'd into a box, then you run a command, then you somehow automatically get a tunnel for that command's UI port plus a local browser window open to the page)
This is nonsensical, there is nothing textual about the UIs being shown here. It doesn't stop being a GUI if you have a 1:1 representation of the concept within character cells. The UX actually matters, and TUIs are generally built for effectiveness and power (lazygit being an excellent example). But once you start adding mouse clickable tabs, buttons, checkboxes etc. you left the UX for TUIs behind and applied the U…
It's a TUI if it uses text to build those elements. You can be effective and powerful in any kind of interface, Just like you can be ineffective and weak in any kind of interface. People like TUIs because they're cool, and work over SSH.
No. All you've done is make a low-resolution GUI.