News for hackers. Stuff that matters.
Re:Stop Making TUIs by joshka on Friday August 21, 2026 @12:55PM (#49390842)
As a ratatui library maintainer, NO - please don't stop making TUIs ;)

As a developer outside of that, I love the scratch the itch apps stuff mentioned in here. I have a vibe coded SwiftUI chess repertoire builder app that fits in that same sort of space that I'm currently working on, where I'd probably not have chosen to explore the idea if not for coding agents.

I agree with the article that the terminal is an odd shape which you're fighting against historical specs, etc. The key observation I have though is that the mismatch of terminal apps and libraries to deal with this are all fundamentally built around character cells and cursor movement plus various CSI/OSC/ASC/DEC/xterm/... protocols which are complex and have varying support and interact in weird ways.

To get a good terminal UX, I think the answer to this is probably to throw all that compatibility mess away and redesign a modern terminal protocol that bakes in accessibility, regions, scrolling, selection, proper keyboard, etc.

I know Mitchell Hashimoto has a bit of a different perspective on this, which seems like it's to define some more protocol stuff and continue to build up on things. I think that probably gets to 95% pretty well. But a 100% good is a full replacement.

Re:Stop Making TUIs by anon7000 on Saturday August 22, 2026 @02:37AM (#49397187)
> To get a good terminal UX, I think the answer to this is probably to throw all that compatibility mess away and redesign a modern terminal protocol that bakes in accessibility, regions, scrolling, selection, proper keyboard, etc.

Why not just… a GUI framework or layout that’s meant to be keyboard driven and information dense?

Re:Stop Making TUIs by jeroenhd on Saturday August 22, 2026 @03:56AM (#49397601)
TUIs run on any OS with minor patches to support quirks, GUI frameworks need a lot of work. TUIs don't need to follow any OS guidelines, cross-platform GUIs always look bad outside of the "main" platform.

If you're only targeting macOS/Windows/Gnome/KDE then the solution is easy: just grab a GUI control set and go ham.

Then there's remote access: you can spawn an X11 app through X forwarding and have a terrible laggy experience on Linux, you can use RemoteApps on Windows to have a good remote experience (but almost no other platform), you can use VNC to have an awful cross-platform experience, or you can use a TUI and have all the graphs and interactivity you need over a responsive, low-bandwidth connection on any combination of client+server.

Re:Stop Making TUIs by wiseowise on Saturday August 22, 2026 @04:43AM (#49397836)
> TUIs don't need to follow any OS guidelines, cross-platform GUIs always look bad outside of the "main" platform.

So because TUIs look universally bad, they're better than cross-platform GUI?

Re:Stop Making TUIs by notpushkin on Saturday August 22, 2026 @05:57AM (#49398191)
> cross-platform GUIs always look bad outside of the "main" platform

qBittorrent looks great on KDE, and would look great on macOS too if they used native icons (I’ve made a theme for that but was too lazy to install it when I was switching laptops). No idea about Gnome and Windows, but probably alright as well.

So, Qt can get you a long way. But you should of course adapt your app to platform conventions and guidelines.

Re:Stop Making TUIs by Dilettante_ on Saturday August 22, 2026 @05:10AM (#49397962)
>So because TUIs look universally bad

You can't stay engaged if the menus don't bleep and bloop at you and confetti rains down on every click? That's a personal problem. A minimal UI is not automatically a bad-looking UI.

Re:Stop Making TUIs by WA on Saturday August 22, 2026 @05:39AM (#49398092)
No, but I want to click to place the cursor in my 10 line prompt wherever I want. I want to double click to mark words. I want to use a scroll bar. I want to copy paste properly and not "23 lines pasted". I don’t want to read docs to find all keystrokes the TUI supports to achieve what I want.
Re:Stop Making TUIs by catlifeonmars on Saturday August 22, 2026 @08:18AM (#49398996)
You can handle mouse events in a TUI

https://ratatui.rs/concepts/backends/mouse-capture/

Re:Stop Making TUIs by yencabulator on Sunday August 23, 2026 @04:28PM (#49412309)
And I want to read proportional fonts, like just about anything except terminals already uses.
Re:Stop Making TUIs by pjmlp on Monday August 24, 2026 @04:28AM (#49416789)
Yeah, already in 1990, what an achievement. /s

https://en.wikipedia.org/wiki/Turbo_Vision

Re:Stop Making TUIs by catlifeonmars on Tuesday August 25, 2026 @12:03AM (#49428939)
I thought that UI looked vaguely familiar, and then I realized that the BIOS on many computers uses that design. I never really connected the dots.
Re:Stop Making TUIs by dirasieb on Saturday August 22, 2026 @02:03PM (#49402140)
>I want to click to place the cursor in my 10 line prompt wherever I want. I want to double click to mark words. I want to use a scroll bar. I want to copy paste properly and not "23 lines pasted"

sounds like your terminal emulator is just crap, terminal and iterm on mac just work

Re:Stop Making TUIs by WA on Saturday August 22, 2026 @04:14PM (#49403415)
iTerm2. Doesn’t work out of the box or something, but I’ll take a look at my config.
Re:Stop Making TUIs by maleldil on Monday August 24, 2026 @07:12AM (#49418104)
> not "23 lines pasted"

If you mean what Claude Code does when you paste longer text, you can just press Cmd-V again to show the full text.

Re:Stop Making TUIs by WA on Wednesday August 26, 2026 @03:57AM (#49445435)
Thanks. Kinda proves my point about TUIs having all kinds of hidden keyboard shortcuts.
Re:Stop Making TUIs by maleldil on Wednesday August 26, 2026 @04:50AM (#49445806)
You're definitely right about that. I couldn't tell you where I found out about this keybind.
Re:Stop Making TUIs by pwdisswordfishq on Saturday August 22, 2026 @04:59AM (#49397917)
> I think the answer to this is probably to throw all that compatibility mess away

> TUIs run on any OS with minor patches to support quirks

So, which one is it?

Re:Stop Making TUIs by Almondsetat on Saturday August 22, 2026 @06:36AM (#49398345)
Those two are not contradictory statements
Re:Stop Making TUIs by embedding-shape on Saturday August 22, 2026 @06:39AM (#49398360)
Maybe not, but they do sit on opposite end of an axis looking something like:

    TUI that runs on any OS |----------------| TUI without any compatibility mess
You really can't have both at the same time, either you have great compatibility (which will be a mess), or you don't, to varying degree of course.
Re:Stop Making TUIs by Almondsetat on Saturday August 22, 2026 @06:59AM (#49398440)
Basically any OS can install any compliant terminal emulator, meaning the cases in which you really have to patch your TUI for another OS are few and infinitely more manageable than GUIs
Re:Stop Making TUIs by Arainach on Saturday August 22, 2026 @07:02AM (#49398458)
Compliant with what? The proposal is "throw out all the compatibility and build some other kind of terminal" in which case nothing is portable.
Re:Stop Making TUIs by TylerE on Saturday August 22, 2026 @08:37AM (#49399131)
How so? The idea is you build all the OS specific stuff into the terminal, not into the programs running INSIDE the terminal. Think Infocom Z-Machine, at the ultimate level, although obviously emulating a full on virtual CPU is overkill.

In any case we can surely do better than emulating DEC hardware from 50 years ago.

Re:Stop Making TUIs by shevy-java on Saturday August 22, 2026 @08:53AM (#49399244)
It depends. If the OS can run e. g. ncurses, you have access to quite a lot of software here, such as htop. Though, I am not sure if it works on windows; but I think it works on OSX. Windows is very strange.
Re:Stop Making TUIs by zbentley on Saturday August 22, 2026 @11:22AM (#49400697)
I really think they are. The reason for terminals’ ubiquity is precisely their age, their age results in them standardizing and accumulating bizarre behaviors.

Even in the microcomputer era, standardizing behavior to where it’s literally everywhere someone might want it takes time (e.g. the browser compatibility wars). Re-standardizing terminal behavior is both chasing a way wider (in terms of the number of places folks expect terminals to work the exact same way) but shallower in feature complexity target compared to browsers, and would necessarily be replacing a widely adopted existing standard behavior. That’s a tall order—I am hopeful for and impressed by the efforts of folks like Hashimoto, but expectations here should be tempered.

Re:Stop Making TUIs by eviks on Saturday August 22, 2026 @07:33AM (#49398655)
> TUIs don't need to follow any OS guidelines, cross-platform GUIs always look bad outside of the "main" platform.

TUIs look bad everywhere, so that's strictly worse

Re:Stop Making TUIs by i_am_a_peasant on Saturday August 22, 2026 @03:33PM (#49403033)
TUIs would be great if they didn't have to render all text the same size, for me that's the main win with GUIs, you have total freedom with what you can do with your pixels.

I would definitely be pro minimalist unicode-character-themed GUIs for what it's worth. Where every graphical primitive is basically a unicode character, without the restriction on font size.

Re:Stop Making TUIs by eviks on Saturday August 22, 2026 @04:02PM (#49403286)
That's not total pixel freedom, you're still limited to text
Re:Stop Making TUIs by leephillips on Saturday August 22, 2026 @03:57PM (#49403238)
Some terminal emulators, for example Kitty, can render text at various sizes (within the same window).
Re:Stop Making TUIs by psychoslave on Saturday August 22, 2026 @08:47AM (#49399202)
There is not much difference between a TUI and a GUI once the premise is "let's start from scatch all other again for each applications". Sure then there is no guideline that comes between idea and implementation. But there is also no built-in accessibility, UX best-practices and many specificity of handling a vast experience of building something stable over a large period of time with many feedback from many different scenario.
Re:Stop Making TUIs by the__alchemist on Saturday August 22, 2026 @10:32AM (#49400167)
> TUIs run on any OS with minor patches to support quirks, GUI frameworks need a lot of work. TUIs don't need to follow any OS guidelines, cross-platform GUIs always look bad outside of the "main" platform.

Have you tried to write a GUI program lately? I suspect things may have changed. I can write one using Qt, EGUI, etc (Or many other options), and it will just work on Windows, Mac, Linux/Wayland, and Linux/X.

Basically, you write your application on top of a GUI framework that smooths over OS differences for you.

Re:Stop Making TUIs by zahlman on Saturday August 22, 2026 @12:52PM (#49401500)
> I can write one using Qt, EGUI, etc (Or many other options), and it will just work on Windows, Mac, Linux/Wayland, and Linux/X.

This is hard to square with the continuing obsession with Electron.

Re:Stop Making TUIs by d-us-vb on Saturday August 22, 2026 @06:57PM (#49404675)
I suspect the u ubiquity of electron persists more because maintaining both web and desktop interfaces is somewhat simplified, and as a corollary, you don’t need a separate JS and C/C++/QML team. Qt has gotten pretty good, but JavaScript and typescript are easier to hire.
Re:Stop Making TUIs by pjmlp on Sunday August 23, 2026 @12:41AM (#49406108)
Pay for cheap labour, get a cheap product.

I thought Claude could do anything nowadays.

Re:Stop Making TUIs by bionade24 on Sunday August 23, 2026 @04:56PM (#49412553)
QML is a Javascript Superset
Re:Stop Making TUIs by d-us-vb on Monday August 24, 2026 @10:20AM (#49420207)
But it runs on Qt, which is most certainly not.
Re:Stop Making TUIs by rtpg on Sunday August 23, 2026 @01:58AM (#49406363)
I think Qt is a bit different here because of Qt Quick etc but I've tried using "native" GUI frameworks a lot and ultimately the web DOM model is pretty nice for iterating easily.

Querying into the DOM and working off of that means you're not futzing about holding onto a bunch of component references for the one thing you might need later on.

Web layout is also pretty easy to just get right, native GUI frameworks have a different kind of layout model that is not as amenable to "arbitrary" data (at least at first blush).

the reactive programming model also works quite well. While there are native GUI frameworks that lean into reactive programming, they tend to be doing a bunch of weird stuff that cause other issues.

And at the end of the day, when you package something like a Qt app it still often ends up being quite chunky.

In the end tho... the simplest thing is if you do web stack you get a web UI _and_ your "native" GUI in one go. Build things once, not twice. Hard to argue against that when that's presented.

Re:Stop Making TUIs by 4k93n2 on Saturday August 22, 2026 @01:10PM (#49401625)
they wont work on android though. thats the main reason i started using more TUIs myself. i needed to be able to run a bunch of python scripts on linux, windows and android/termux. or if any of the linux phones ever matures, or sailfish, then the same scripts will run thereas well, probably without any modifications needed
Re:Stop Making TUIs by okanat on Saturday August 22, 2026 @05:31PM (#49404059)
KDE has a framework based on Qt's QML that works on Android. It is called Kirigami. They have written apps and even a complete Plasma Mobile using it. The apps work both on Android and Linux.

Mobile has significant paradigm changes that makes using both terminals and traditional GUIs harder anyway though. I do expect the need for completely different cross-platform libraries for mobile UIs.

Re:Stop Making TUIs by pjmlp on Sunday August 23, 2026 @12:54AM (#49406148)
Termux is not the right way to execute Apps on Android, Pydroid does the job.

Also, Qt does support Android development.

Re:Stop Making TUIs by 4k93n2 on Sunday August 23, 2026 @01:51AM (#49406334)
why is it not right? ive been using it for years and everything works just fine
Re:Stop Making TUIs by pjmlp on Sunday August 23, 2026 @02:20AM (#49406449)
It is trying to fit GNU/Linux into Android/Linux, on a model that has only worked so far because internal politics have prevented the replacement of Linux kernel with Zirkon.

The official NDK documentation on what is supported for NDK written code on non rooted devices, and the hurdles that Termux faces to keep running on standard Android images via PlayStore distribution, show why it isn't right.

Re:Stop Making TUIs by messh on Saturday August 22, 2026 @10:55AM (#49400424)
Html has also some of these properties, targeting the browser. Don't get me wrong. I do like TUIs, they are light weight and compose very nicely with the rest of the terminal (eg tmux). Also, i generally prefer just cli commands over tuis when possible.
Re:Stop Making TUIs by zbentley on Saturday August 22, 2026 @11:16AM (#49400635)
That ubiquity is the reason for the limitations of terminals/TUIs discussed in grandparent. Those two are not separable: they’re everywhere precisely because they target the lowest, oldest common denominator (teletype console behavior assumptions from the 1960s).

I expanded on this point nearby: https://news.ycombinator.com/item?id=49400697

Re:Stop Making TUIs by fsloth on Sunday August 23, 2026 @04:14AM (#49406979)
[delayed]
Re:Stop Making TUIs by ambigious7777 on Sunday August 30, 2026 @09:54AM (#49498687)
i appreciate still having my same tools when i switch from linux to windows devices
Re:Stop Making TUIs by inigyou on Saturday August 29, 2026 @01:04AM (#49487023)
Sending drawing commands to an X server is no more difficult than sending escape code sequences to a terminal. Simpler, even, because it's actually designed for that. And yet it's also more flexible. If your GUI framework of choice is limiting you, you're welcome to write one, just like you're already writing a TUI framework.
Re:Stop Making TUIs by Brian_K_White on Saturday August 22, 2026 @05:19AM (#49398007)
Countless reasons.

Invent a gui client environment that is universal, works the same way everywhere, over any kind of channel, and is already implimented and supported everywhere, and utterly weightless in all dimensions (ram/cpu/network), and then you might be able to ask that question without it being incredibly ignorant.

Today the closest you might be able to say is web/electron, which is gross on all counts. If anything the closest is X11, which is not remotely close enough.

That's why not just...

Re:Stop Making TUIs by teddyh on Saturday August 22, 2026 @08:00AM (#49398858)
Re:Stop Making TUIs by crostlybostly on Saturday August 22, 2026 @05:37AM (#49398088)
HTML/Javascript would like a word
Re:Stop Making TUIs by flossly on Saturday August 22, 2026 @06:04AM (#49398214)
we need a way to access locally running web apps without doing an ugly http://localhost:8022 and having to remember that.

I'd say http://localapps should give an overview of all web apps running locally, with links to them. Those links should follow a naming scheme where the hostname ends with `.local` or smth.

So: http://claudecode.local

Re:Stop Making TUIs by singpolyma3 on Saturday August 22, 2026 @08:16AM (#49398979)
Bring back installable PWA on desktop
Re:Stop Making TUIs by mr_olive on Saturday August 22, 2026 @07:00AM (#49398446)
Hah, I was dealing with this problem today.

My approach: Add entries for my localhost apps to `/etc/hosts`, and set up nginx as a reverse proxy.

Now when I go to `http://myapp.local` in the browser, `/etc/hosts` tells it to go to `localhost:80`. The http server sitting there knows which port to send the request to. I also made a systemd service that starts nginx automatically.

Now I have meaningful URLs for local apps, and I don't have to remember which one is listening on which port.

Re:Stop Making TUIs by fc417fc802 on Saturday August 22, 2026 @06:32AM (#49398337)
Won't that be cluttered by various random processes listening via 0/0? Perhaps we need a standardized service that web apps can register with.
Re:Stop Making TUIs by antonvs on Saturday August 22, 2026 @09:19AM (#49399483)
> I'd say http://localapps should give an overview of all web apps running locally, with links to them.

Malware will thank you.

Re:Stop Making TUIs by iskra on Saturday August 22, 2026 @10:23AM (#49400055)
Rather than typing http://localhost:8022, name each app and put them behind one local proxy:

1. In /etc/hosts (or dnsmasq): 127.0.0.1 ourapp.test 2. Caddy in front: ourapp.test { reverse_proxy localhost:8022 }

Caddy auto-provisions local certs, so you get https://ourapp.test, no ugly ports and no "not secure" prompt.

For the overview idea: a tiny local dashboard that scans common dev ports (3000, 5173, 8080...) and lists each running app by name is a ~100-line utility. This is exactly the kind of small tool I build, happy to make a quick version for you.

Re:Stop Making TUIs by flossly on Tuesday August 25, 2026 @07:12AM (#49431912)
Cool! I'd say we need a big linux distro to buy into it, so that it provides it's config-panel and package manager UI in this format.
Re:Stop Making TUIs by NBJack on Saturday August 22, 2026 @10:21AM (#49400038)
Definitely not weightless. So much bloat has been dedicated to various frameworks for it, and modern browsers are notorious for how much RAM they require. I'm particularly reminded of this each time I try to visit websites on one of my older Raspberry Pis. You are just pushing much of that complexity and overhead to the client.

That same Pi won't even blink at a local TUI.

Re:Stop Making TUIs by Brian_K_White on Saturday August 22, 2026 @07:56PM (#49405010)
Are you insane?

No just ignorant most likely. I can see how a child might think that an http/html session qualifies as providing all the same utility of a tty. Well it does not remotely by orders of magnitude.

I already said in the comment to begin with: "The closest you could say is web/electron, which is gross on all counts."

Re:Stop Making TUIs by trueno on Saturday August 22, 2026 @06:06AM (#49398221)
there's a million gui frameworks under the sun and i still haven't found one that feels like what everyone has been asking for:

good dx, cross platform, fast, not ugly.

pick i dunno 2 or 3.

tui's get to check 2 or 3 of these just like any other gui library. somehow there still isn't a silver bullet here.

now i personally don't build tuis but guake style dropdown simple command and i have some other thing someone made open immediately running in ghostty? hell yea. with that said yes there are some stupid tuis out there that are anything but simple.

Re:Stop Making TUIs by singpolyma3 on Saturday August 22, 2026 @08:14AM (#49398965)
Except web. Which inexplicably got all of these when no one was looking
Re:Stop Making TUIs by TylerE on Saturday August 22, 2026 @08:38AM (#49399134)
Not fast.
Re:Stop Making TUIs by zbentley on Saturday August 22, 2026 @11:26AM (#49400730)
Not “not ugly” either. The flexibility is too high and standardization of UX is too low. Technically, we’re missing adoption of default standard toolkits like swing or GTK, and politically a11y/compliance checkers are a far cry from something like the HIG of old.
Re:Stop Making TUIs by singpolyma3 on Saturday August 22, 2026 @09:30AM (#49399584)
How so?

You can make slow things with it of course but it's not inherent.

Re:Stop Making TUIs by psychoslave on Saturday August 22, 2026 @08:56AM (#49399261)
That depends what is build and how. Granted that a modern web browser is indeed an order of magnitude heavier than an OS, once that ticket is paid anyway, one can built very far, without relying on any additional bloat that contemporary web frameworks puts on top of it. There is not that much more data to send though HTTPS to bring a far more convenient UX than what raw text bespoke tweaks can offer over SSH.
Re:Stop Making TUIs by pjmlp on Monday August 24, 2026 @04:34AM (#49416840)
Fast and good DX, not really, unless we are comparing it to command line tools, instead of 4 GL and RAD tools from the 1990's.

Especially when I keep bumping into Electron apps.

Re:Stop Making TUIs by barnabee on Saturday August 22, 2026 @08:45AM (#49399183)
Agreed. This is exactly what I want, ideally with components and libraries and panels and data shareable and extendable between applications.

The closest in spirit is Probably something like Dear ImGui[0] and the ecosystem of components and apps built with it, but it's not quite there for me. Something is missing.

[0] https://github.com/ocornut/imgui

Re:Stop Making TUIs by tyre on Saturday August 22, 2026 @09:08AM (#49399378)
charm.sh builds many such things. I love them and their personality.
Re:Stop Making TUIs by christophilus on Saturday August 22, 2026 @09:08AM (#49399380)
It’s trivially easy to run a TUI in a container. Not so much with GUIs. And, since I run as much as possible in containers, and as little as possible on my host machine, I much prefer TUIs.
Re:Stop Making TUIs by yencabulator on Sunday August 23, 2026 @04:30PM (#49412323)
Wayland runs over a UNIX domain socket you know.

And if you meant "virtual machine" or "cloud" by saying "container", `waypipe ssh myhost`.

Re:Stop Making TUIs by pjmlp on Monday August 24, 2026 @04:29AM (#49416800)
It is as easy as any X Windows or RDP connection.
Re:Stop Making TUIs by ziotom78 on Sunday August 23, 2026 @06:58AM (#49407815)
BearLibTerminal might be something on this line, although its purpose is mainly for developing rougue-like games. It simulates a terminal in a GUI with a high-level API

http://foo.wyrd.name/en:bearlibterminal

Re:Stop Making TUIs by joshka on Sunday August 23, 2026 @11:19PM (#49414867)
yeah, something along those lines - but more robustly defined.
Re:Stop Making TUIs by fc417fc802 on Saturday August 22, 2026 @03:27AM (#49397445)
> To get a good terminal UX, ...

At that point you're just inventing a new DOM variant and aren't fundamentally different from any other opinionated GUI framework. The value of the terminal for me is the minimalism. I absolutely despise all these new "features" that get added via protocols. I _want_ the boring grid composed entirely of extremely primitive character cells where WYSIWYG in terms of any underlying abstraction. The only innovation I welcome in this space are improvements to portability and speed.

My snarky response to the author's title would be that you can take your GUIs and all the janky flashing lights they entail and shove them up your ass.

Re:Stop Making TUIs by joshka on Saturday August 22, 2026 @08:52AM (#49399229)
The problem is that cells don't compose well as an accessibility thing. You need a DOM equivalent in order to realistically do a bunch of things that are meaningful at an app level. TUI libraries are all basically doing that DOM thing already - just custom and treating the final shippable product as the cells, positions and imperative instructions for how to tell a terminal what to do. I' just saying that a more declarative interaction is very likely the sort of simple and boring that helps portability (long term) and speed.
Re:Stop Making TUIs by fc417fc802 on Sunday August 23, 2026 @12:27AM (#49406068)
Upon reflection, I think the only thing I'm opposed to is visible "features". As long as the final output remains a dumb grid of cells with extremely limited capabilities I can see where it would be useful for accessibility (or other) purposes to have a bunch of metadata in a standardized format describing the model that underlies the final output. A number of times I've been frustrated by the lack of additional channels when processing streams of data.
Re:Stop Making TUIs by torginus on Saturday August 22, 2026 @08:09AM (#49398929)
I have a question - I've briefly looked at the API, and it seems like a mostly general-purpose user interfance library.

What do you think of replacing the 'render' part with something that's more like a generic UI? You could keep the UX the same, yet your app would look like a desktop app (or at least close to it).

Trying to fit in the limitations of 80x25 text rendering is cool, but there's nothing in the underlying architecture that of modern graphics display that's predisposed to that, it all ends up as GPU commands.

I'm sure you could get most of the way to what I'm describing with just replacing the font/character set with one that renders things like borders in greater detail.

Hell, you could even add this as post-processing. You look at the terminal output with cellular automata like rules, and try to render UI primitives fitting that.

Re:Stop Making TUIs by joshka on Saturday August 22, 2026 @08:47AM (#49399198)
If you're redesigning a protocol layer, then I'd say you still want to target fixed size cells as the unit of rendering. It's just not the central abstraction like it is in the current terminal approach. Because you're one step above here, you have th ability to do better border handling. There's a lot a things you miss trying to force borders through a character set thing (e.g. missing characters depending on your font, missing ability to position borders naturally, interaction with background color, adjustment of size and space of rendered text due to interaction with unicode characters and fixed positioning) ...

But in general, going with a fresh new protocol allows you to do a bunch of things semantically that are currently done as pure graphical stuff and that's useful.

Re:Stop Making TUIs by torginus on Saturday August 22, 2026 @02:15PM (#49402250)
I was suggesting something that could be done without changing the protocol itself.

From what I undestand, the terminal is essentially a concatenative text buffer extended with control commands allowing you to move the cursor (pen) to draw more sophisticated stuff, and update UIs.

The logical way to extend this would be to allow genericdrawing commands over the protocol, at which point the whole thing starts sounding like X11.

I'm sure the Unix people at MIT in the 80s saw this as the natural evolution from text terminals to graphics based ones.

Not saying this is a bad idea, but sounds suspiciously like a retread of history.

Or you might want to stop before that, as you suggested, at targeting fixed size cells for rendering, and keeping the console-like UX throughout. I'm sure there's a sensible intermediate step, but if you want to do things like displaying graphs or images (turning the terminal into something that's halfway between a terminal emulator and a Jupyter notebook), it'd be awkward to respect the character grid and the non-square characters themselves.

I'm curious what you think about how far this new protocol should go, and in what direction. You mention 'semantics', as describing behavior, not just what gets drawn to the screen, which neither X11 nor tty does.

Re:Stop Making TUIs by joshka on Saturday August 22, 2026 @04:11PM (#49403369)
The problem succinctly is when the terminal emulator only sees cell values and instructions it can't do anything more with things. Two really good examples are implementing accessibility well, and scrolling / changing things above the terminal pane without rewriting the whole history.
Re:Stop Making TUIs by torginus on Saturday August 22, 2026 @05:43PM (#49404160)
What you describe sounds a lot like the HTML/CSS split, with having a separate semantic/display data. I think that's a rather large jump from the 80x25 model, retrofitting that much data sounds like quite the challange.

Not sure how you're planning on doing that, can you incrementally extend the current model, or will it require a completely new protocol?

Re:Stop Making TUIs by joshka on Sunday August 23, 2026 @07:07PM (#49413481)
New protocol entirely. The existing stuff is too baked as having positioning, movement, cells as the unit of abstraction. You need to have that available, but not as the core abstraction level. The core has to be areas, words, layout, etc. Not: "move to 20, 35, start red, bold, print border characters"
Re:Stop Making TUIs by torginus on Monday August 24, 2026 @03:24AM (#49416262)
Cool, thanks for answering! I don't really want to take any more of your time, is there some place I can read up on this new proposed protocol?
Re:Stop Making TUIs by joshka on Monday August 24, 2026 @08:01PM (#49427472)
It's mostly something I'm thinking a bunch about recently. Nothing written up yet aside from the above. I'd go read Mitchell Hashimoto's Lobsters interview fora different take and see how that resonates with you as well as the recent blog posts about TUIs and accessibility.
Re:Stop Making TUIs by fractorial on Saturday August 22, 2026 @09:01AM (#49399313)
Damn, what an epic library name.
[dead]
Re:Stop Making TUIs by joshka on Saturday August 22, 2026 @04:20PM (#49403473)
I have built a pretty full version of that idea in rust (codex tui2). There's a while tonne of downsides that make it basically impossible to really get to 100% good on this.

> Under the hood it's still a terminal app, but from the UI author's perspective you're not fighting terminfo, CSI sequences, or varying terminal support. You get proper cursor tracking, scroll regions, and editable text areas out of the box.

All that is not true. Take scrolling for example. Each terminal emulator implements this subtly differently (mouse/trackpad/speed etc.), scrolling will never feel native unless you push the control of it into the terminal emulator.

There's more than that, each and every point on this becomes something that you have a gap between native and the terminal emulator that you're building to run in the terminal.

See https://github.com/openai/codex/issues/8344 and https://github.com/openai/codex/pull/9640

Claude code and gemini have both had various versions of the same idea at times. I'm unsure where they ended up.

Re:Stop Making TUIs by vatsachak on Saturday August 22, 2026 @12:22PM (#49401225)
So...emacs
Re:Stop Making TUIs by pjmlp on Saturday August 22, 2026 @02:19PM (#49402297)
Which is kind of a poor man's Lisp Machines.

https://interlisp.org

Re:Stop Making TUIs by internet2000 on Saturday August 22, 2026 @12:48PM (#49401462)
Not only I want people to stop making TUIs, I want you to stop maintaining your TUI library!
Re:Stop Making TUIs by tptacek on Saturday August 22, 2026 @12:55PM (#49401520)
Ratatui is such great work.

The New Terminal, the complete break from VT100, is I think the most powerful rebuttal to what I'm saying about TUIs.

My take is that the Morlocks should pack everything that is great about TUIs (and there are great things about them) and move them upstairs to live alongside the Eloi in GUI-land. Let 1000 Bloomberg terminal interfaces bloom.

But there's another even more ambitious take on this, which is to take everything that's pleasant and good about Eloi world and bring it down into the Morlock caves. I don't think you can accomplish that so long as you're drawing interfaces with punctuation characters, but there's nothing to say a terminal has to work that way; you can have a terminal with rich out-of-band-signaled UI. Not just, like, Kitty graphics, but something more like a real terminal that is meant from day 1 to work with all the complexity of a Bloomberg terminal.

You could have had it in 2010, but it's a king hell mess to put together, and you'd sort of assume nobody was going to use it (because it's a break from VT100 compatibility). But that doesn't matter anymore! We are the music makers, &c &c.

I think a lot of very smart people assume we're going to build up from VT100 to something incrementally but significantly better (Ghostty is already materially better than anything I'd used prior). But I hope those people eventually set their sights higher.

Re:Stop Making TUIs by joshka on Saturday August 22, 2026 @04:06PM (#49403325)
> as you're drawing interfaces with punctuation characters

Yeah, in my hypothetical new protocol, the character cell is still there, but it's not the element that drives the main abstraction. The layer above that being more semantic is where the smarts is. So borders, interactive areas, mouse hit mapping to elements, etc. ends up being built into the protocol rather than being a cell level thing. Cells having proper borders being similar to how they allow for underline, being able to have both images and text, ...

I think it's important to do something about the VT100 +kitchen sink stack and to have that as something that still works with that in areas of the new terminal proto. I've got a slopcoded rust library in the works that's about fully mapping the full list of terminal protocols and related things in one coherent library (VT100, ECMA48, DEC modes, iTerm extensions, Kitty, ...). From there I think making that fairly isomorphic with the terminal emulator layer (I have a RIIR ghostty slopfactor there too that fits).

I think ghostty / superlogical looks at this from the perspective of doing pty things and then transfering that calculated state across the wire while doing fun stuff with windows, panes etc. with replay and that sort of thing. I think this is valuable too.

I suspect that there's possibly a way to do a bit of a hybrid on this - normal pty things with the extra sidecar of more semantic structured, but it'll make things more complex for app builders on that side of things.

(On another comment I saw you mentioned "couldn't help noticing how much of the tedious work of putting a TUI together". I think probably textual in python is probably the best of the low ceremony libraries for making TUIs if you haven't checked that out yet. I think someday there will be a good Rust library that has that level of put together-ness. I have some ideas on this for ratatui and have seen a bunch of things that are directionally right for this, but nothing that gets close yet).

Re:Stop Making TUIs by quantumwannabe on Saturday August 22, 2026 @01:43PM (#49401963)
Grok Build uses your library and it has the best TUI of any app I've ever used. It has a lot of features that we take for granted in GUIs like scrollable regions, buttons, collapsible panes, and text selection.

I don't know why Codex and Claude Code haven't switched over; both apps have a terrible UI in comparison.

Re:Stop Making TUIs by joshka on Sunday August 23, 2026 @07:15PM (#49413535)
Codex uses Ratatui also since June last year. You might be interested to read https://github.com/openai/codex/issues/8344

There's a lot of things you can do to get to 90-95% fidelity with a normal scollable terminal, but that last 5-10% is impossible. And it's because the you're throwing away a bunch of information about mouse movements, clicks, scrolling, keyboard on the input side and all the layout info on the output side (the terminal just sees cells, locations, etc.).

A good analogy is what if your webserver could only send pixels, not html. And receive raw mouse movements. The amount of stuff you have to do to reconcile that across operating systems and hardware would be enormous. That's what you realistically have when you're writing a tool that reimplements all the bits from a terminal emulator in a tui.

Re:Stop Making TUIs by chamomeal on Saturday August 22, 2026 @01:59PM (#49402111)
I’ve found some of my favorite TUI apps by scrolling around in the built-with-ratatui page. I have always bounced off of rust but ratatui must be a great library!!