Top
Best
New

Posted by underdeserver 1 day ago

Stop Making TUIs(sockpuppet.org)
379 points | 498 commentspage 10
ngvrnd 9 hours ago|
user interfaces are for users. people who deal with words may prefer an advanced TUI. Others may find graphical interfaces more useful. describe, don't prescribe. let a thousand flowers bloom.
bentt 14 hours ago||
TUIs are by definition keyboard first.

TUIs are a creative constraint.

TUIs are an invitation for programmers.

TUIs are doing "less" to render.

TUIs don't need to be "responsive".

Hello World is TUI.

yeodev 16 hours ago||
I think OP is missing the point of TUIs: They kinda work everywhere. While I need to fuck around with a operation systems native UI libraries like WinUI, SwiftUI, GTK, etc. I can just build an app in the terminal and be fine with it running on almost all platforms.

I'd take TUI apps over electron apps everytime as long as the UX is good.

lo0dot0 12 hours ago|
No. TUIs do not work everywhere. They can break because of terminfo which I really don't want to deal with. I hate wasting time on such configuration issues.
migueldeicaza 11 hours ago||
Possible, but rare in practice.

Nowadays, you are more likely going to struggle with plugging your laptop into a 320Volt outlet than have a terminfo problem.

trollbridge 6 hours ago||
LLM agent harnesses make it possible to do: CLI, TUI, REST API, web front end + Electron, native (I do macOS first, which then makes iOS/iPadOS almost trivial, followed by Android), and if I’m feeling ambitious, Windows (native) and Linux (usually Qt).

It’s much easier for the clanker to loop on testing / improving the TUI than a real GUI. It also means it can work on the app without an API/REST/HTTP/Java/Script ball of mud in the middle.

cush 10 hours ago||
I wonder if devs are flocking to TUIs to gatekeep against normies building apps
skeledrew 1 day ago||
Making TUIs isn't the issue. Making them with JS/TS, and in general an ecosystem designed for the web, is the problem. I've used some really good TUI apps in the past, but all these new ones mostly based on web tech are just... sloppily bad. Probably because the dev would rather be in the web browser where it's naturally colorful and scripts can run wild, but mostly-static terminal is where things are currently at. And they're using LLMs, which don't have sufficient data on web-tech-in-terminal since it wasn't really a thing until now, which also ensures they will likely never gain enough data on decent patterns since almost nobody will be engineering said patterns, creating a permanently slop-ridden cycle as future models only have slop projects to learn from.
mcapodici 12 hours ago||
TUIs allow you to have infinitely many running in tmux and also work over ssh so there is that.
lo0dot0 12 hours ago|
Actual GUIs also work over the network, either as a web service rendered in the browser or a desktop app with a backend network connection.
Kon5ole 15 hours ago||
The aggressive headline is a hook which is what bloggers have to do I guess, but it doesn't need to be polarizing. The argument boils down to "If you made a TUI only because making a native app is hard, then LLM's fix that for you now".

Making GUI apps has been way too hard on all platforms since forever. Frankly I think it's gotten worse for 20 years. People started fleeing to web wrappers like Electron to escape the horrors of native UI development.

So if that was the reason why you made a TUI, take heed. LLM's can chew through UI frameworks for you.

But I solidly believe TUIs are often better than GUIs even if they were equally easy to make. They liberate your app from having to follow the fracture and fashions of GUI's - Liquid glass, Windows 8, SwiftUI, WinUI3, QT, GTK or whatever. A TUI allows muscle memory that you learned on Solaris in the 90s to work fine in windows 11 in 2026.

archonis 11 hours ago||
>> Because I assume that agents work better with a filesystem to grovel

What the what now?

More comments...