News for hackers. Stuff that matters.
Re:Why TUIs Are Back by giancarlostoro on Sunday May 03, 2026 @03:44PM (#48000644)
Because nobody is investing in native UI development. Electron is proof that if there were a simple to use GUI stack that companies would adopt it.
Re:Why TUIs Are Back by thayne on Sunday May 03, 2026 @04:15PM (#48000951)
I don't think it is lack of investment necessarily, so much as not building the right thing.

What we need is a framework that is easy to use, cross platform, open source, and ideally can be used from your programming language of choice.

Re:Why TUIs Are Back by victorio on Sunday May 03, 2026 @05:04PM (#48001472)
You are not going to believe this... (joking)
Re:Why TUIs Are Back by einpoklum on Sunday May 03, 2026 @05:48PM (#48001906)
Are the available FOSS cross-platform frameworks really not that good?

There's at least Qt, GTK, umm, and, I guess Juce and wxWindows, right? Oh, I see there are more:

https://en.wikipedia.org/wiki/List_of_platform-independent_G...

Can you explain what's deficient about the first two I mentioned?

Re:Why TUIs Are Back by MrDOS on Sunday May 03, 2026 @06:17PM (#48002172)
> Qt

Arcane build system. I mean, I guess it technically supports CMake these days, but I have never been able to get anyone else's Qt project to build without much gnashing of teeth.

Emulated native widgets try for pixel-perfect, but tend to feel wrong somehow.

> Gtk

Outside of a Linux/Gtk native environment, Gtk applications are awful. Take GIMP on macOS, for example: it's had window focus issues (export dialog getting lost behind the main application window) literally ever since Gtk on macOS dropped the XQuartz dependence. And that's the flagship application for the toolkit.

Re:Why TUIs Are Back by Pay08 on Monday May 04, 2026 @12:11AM (#48004540)
CMake support in Qt is perfectly fine nowadays. There are some (optional) custom commands you can use, but generally it's just plain CMake.
Re:Why TUIs Are Back by einpoklum on Monday May 04, 2026 @03:04PM (#48013396)
So, your critique of Gtk sounds convincing, but about Qt, you seem to be admitting they're offering a less-horrible way to build than how things used to be.

I looked at this: https://doc.qt.io/qt-6/cmake-get-started.html ... and I'll admit they seem to be hiding some nasty stuff under the hood. But it still seems workable. I guess the devil is in the details?

Re:Why TUIs Are Back by hombre_fatal on Sunday May 03, 2026 @06:34PM (#48002313)
GTK 3 hello world is 150-200mb. They really messed up since GTK 2 was 30mb (like macOS AppKit).
Re:Why TUIs Are Back by WhyNotHugo on Monday May 04, 2026 @03:53AM (#48005858)
GIMP itself is 62MB on my host, I'm not sure what kind of hello world you're building that's 3x that size.
Re:Why TUIs Are Back by einpoklum on Monday May 04, 2026 @10:50AM (#48009470)
Maybe GP means on non-Linux systems? When you have to "vendor" a large number of libraries?
Re:Why TUIs Are Back by hombre_fatal on Monday May 04, 2026 @04:54PM (#48014839)
Dunno, try it yourself. I wrote the hello world with C (12 lines?) and launched it on NixOS in Wayland (sway or niri). Maybe non-Wayland does better?

Granted, not the best measure of memory usage. But the GTK 2 version was 30mb.

Re:Why TUIs Are Back by skydhash on Sunday May 03, 2026 @07:35PM (#48002771)
> cross platform

That's one word that should never been used in an design meeting. None of the GUI I've used has managed to do this right. Even Emacs and Firefox. The platform are totally different (and in the case of Linux/Unix, there's a lot of different HIG competing). So trying to be cross platform is a good illustration of the lesson in https://xkcd.com/927/

The best bet should be a core with the domain with a UI shell. And then you swap the shell according to the platform.

Re:Why TUIs Are Back by Gigachad on Sunday May 03, 2026 @07:45PM (#48002831)
I want my applications to look consistent across platforms. Why would I want discord for example to look entirely different between MacOS and Linux? With the current state of things, once I use the app anywhere, I'll know where everything is on any platform.
Re:Why TUIs Are Back by skydhash on Sunday May 03, 2026 @07:57PM (#48002925)
Take a good look around and check how often people do really change computer platform. And you already have so many things that are different that the "same look" is just an excuse. Gnome, KDE, macOS, Windows does not have the same UX in their file explorer which is a basic utility that everyone has to use. Same with connecting to a WiFi and creating a new user account.

So why would you want Discord to be consistent, when you're mostly using the same desktop (or switch between at most two) for hours.

The thing is when HIG were followed instead of everyone trying to create their "brand", everyone knows where the common actions were. You learned the platform and then can use any app. With the new trend, you would only have one computer, but any new app is a new puzzle to figure out.

Re:Why TUIs Are Back by Gigachad on Sunday May 03, 2026 @10:47PM (#48004066)
I don't really have any issues working out how to use modern electron apps, they all follow very simple UX patterns, I find them much easier to use than the average native wxWidgets/qt app. Simple, consistent UI is less about the color scheme and border radius being consistent and about things being simple and well laid out on a higher level.

Two apps can have different CSS while being easy to understand because the core flows and ideas are the same. While many older native apps feel like junk draw UI with crap thrown everywhere and weird app specific quirks and patterns. Even if it all does use native inputs and windows.

Re:Why TUIs Are Back by GoblinSlayer on Monday May 04, 2026 @04:41AM (#48006126)
Electron apps use the usual web 2.0 forced keyboard focus antipattern which breaks page up and page down scrolling, so they are difficult to use. Also blurry text rendering.
Re:Why TUIs Are Back by thayne on Sunday May 03, 2026 @08:30PM (#48003157)
> The best bet should be a core with the domain with a UI shell. And then you swap the shell according to the platform.

I've rarely seen that turn out very well. Typically it works ok on whatever desktop main developers use, and not so much on the others. That means using multiple frameworks, witht their own idioms and quirks and having to repeat a lot of work. Unless your UI is very simple it is pretty expensive to maintain multiple separate versions of it.

Re:Why TUIs Are Back by skydhash on Monday May 04, 2026 @07:15AM (#48007208)
The best way I’ve seen this implemented is having the domain be a library or a protocol/server. For a lot of saas, we already have people writing the mobile versions and the web version..

Yes. It’s more work than dumping Electron on users. Quality often is.

Re:Why TUIs Are Back by mghackerlady on Monday May 04, 2026 @09:45AM (#48008696)
It's not even that cross platform is necessarily bad, it's that we have so many cross platform toolkits and they compete with native ones.

I think we'd all be better off if we just declared qt the standard gui library and rid ourselves of the chaos we find ourselves in

Re:Why TUIs Are Back by bbkane on Sunday May 03, 2026 @03:55PM (#48000749)
Contrary to what the article says ("but Google gave up on the project before a real product was launched"), I think Flutter work continues and adoption is increasing
Re:Why TUIs Are Back by airstrike on Sunday May 03, 2026 @05:43PM (#48001853)
I don't really want Dart tbh
Re:Why TUIs Are Back by danpalmer on Sunday May 03, 2026 @07:54PM (#48002903)
I dislike Dart, but it does work really well for Flutter. I think if you treat it as a Flutter DSL it's easier to put up with.
Re:Why TUIs Are Back by serial_dev on Sunday May 03, 2026 @06:24PM (#48002238)
The article (as I read it) says that Google gave up on the new operating system (where Flutter would have been the default UI toolkit).

I’m not sure if Google actually already gave up on Fuchsia, I’d be surprised if the work actually stopped, but it’s clear now that it will not be a panacea and if it will ever get released and gets some traction, it’s still like a decade away from becoming a major OS.

Re:Why TUIs Are Back by mghackerlady on Monday May 04, 2026 @09:42AM (#48008663)
They laid off most of the people on the Fuchsia team so it isn't getting as much work, but Fuchsia is used on their nest stuff iirc
Re:Why TUIs Are Back by giancarlostoro on Monday May 04, 2026 @11:23AM (#48009851)
One of my former coworkers / dev friend is primarly a Flutter dev, and he's about to give up on it because finding Flutter jobs has become a pain.
Re:Why TUIs Are Back by tootie on Sunday May 03, 2026 @04:11PM (#48000895)
Zed did. I know it has it's fans, but it doesn't seem to be generating a stampede of adoption despite what looks like a monumental effort to build a GUI system from the ground up.
Re:Why TUIs Are Back by jbvlkt on Sunday May 03, 2026 @05:31PM (#48001729)
What I do not like on Zed or electron GUIs is lack of customization. Older IDEs using sdks like Swing, JWT, QT, GTK etc. allowed user to design its user interface using drag and drop. ie compare older IDEs like eclipse or idea and try to create layout which fills screen with information important for you. And then try to do the same with vscode or zed. I like functionality and speed of zed but UI customization is too limited for me. It might be design choice or sdk limit I am not sure.
Re:Why TUIs Are Back by landr0id on Sunday May 03, 2026 @05:57PM (#48001979)
Their GUI system (GPUI) is not very mature for use outside of Zed. GPUI is basically a UI framework in the truest sense: a framework for building UI... frameworks/components. It has core functionality for async execution, an ECS for grabbing shared resources, and a div.

It's basically like building a website with div and basic CSS.

gpui-component exists: https://github.com/longbridge/gpui-component

Up until sometime late 2025 GPUI wasn't even on crates.io, and it seems like the GPUI-component ecosystem still promotes using git deps. It was also in "read the code for docs" state for a very long time

It's been a while since I've used it, but there were weird things missing too like the Scollbar was located in Zed's UI component crates instead of core GPUI. Arbitrary text selection also is not possible, which is something I really value about egui.

Re:Why TUIs Are Back by AlienRobot on Sunday May 03, 2026 @04:18PM (#48000985)
To me the worst case is trying to develop some small utility like a tool to search in files using regex. Because if you are developing something large, the amount of time you spend dealing with packaging, distribution, etc., is small and you don't care about file sizes.

But if I want to, say, develop the app for Windows. That is easy. You get a tiny binary to just opens a form and runs with a double click. No install necessary.

The same thing on Linux? Impossible. There is no guarantee the machine has any version of GTK or Qt installed at all, so to be self-contained you need to ship the entire OS. Now your file size is huge. I can't use Python, because now Windows users need to have Python or I have to ship an interpreter.

The only plausible alternative is something like Java. Now you have a single .jar file that runs on any system. But then Oracle changed the license, and JavaFX is no longer part of Java (Swing still is).

Honestly, I just want to display a menubar with keyboard shortcuts. Why can't there be a menubar VM or something that gives me access to a menubar on all OS's without having to deal with all of this. We are already shipping the entire browser with Electron. That is stupid. The way it should work is users install a something like Flash but for desktop apps and every app just uses that platform.

It's probably easier to ship a DOS game than a desktop app because everyone who wants to run a DOS game will just have a DOS emulator installed.

Re:Why TUIs Are Back by einpoklum on Sunday May 03, 2026 @05:50PM (#48001921)
> There is no guarantee the machine has any version of GTK or Qt installed at all, so to be self-contained

So don't be self-contained. I mean, you depend on an X server or Wayland, right? So why not depend on GTK or Qt being available?

(Of course, it _is_ tricky to be able to depend on any of several versions of these, but still.)

Re:Why TUIs Are Back by AlienRobot on Sunday May 03, 2026 @06:13PM (#48002143)
What I mean is that on Windows you can just ship an 100kb .exe and forget about it and it's still going to work 20 years later.

On Linux that doesn't happen. First of all you HAVE to ship the source code if you want it to keep working on every machine because people need to compile it on their machine for it to work, so you're practically forced to open source your desktop app. I know the notion of having a closed source app on Linux sounds weird, but it's more weird that this isn't an option as a side-effect of the how the whole system is designed. Second of all, even if you do ship the source code, you're going to be forced to maintain it. If you made an app in GTK 1 (which looks beautiful, by the way, compared to modern GTK), people won't be able to just install it because GTK 1 is so old that it's no longer in the repositories.

An app made in Java 8 runs in the modern VM. An app made for Windows 95 still runs on modern Windows.

It's only on Linux that I feel like the developer is pressured to open source it and make it the user's problem because the system won't provide support.

Re:Why TUIs Are Back by okanat on Sunday May 03, 2026 @06:53PM (#48002454)
I'm not defending this but there was (or has been) enough political motivation and intentionality in GNU/Linux systems to make binary compatibility a hassle. People actually made decisions against backwards compatible APIs, intending to cause issues and forcing open-sourcing.

Binary compatibility means closed source has a chance to grow in an ecosystem. It requires "responsible" developers to put more effort into designing APIs and keeping them alive. It adds complexity that requires a more stable set of long-term developers; in contrast, the constant churn in FOSS requires lower barriers for contributions. With stable APIs/ABIs you have to live with decade-long mistakes. You cannot "just fix it" in a next major bump.

Re:Why TUIs Are Back by GoblinSlayer on Monday May 04, 2026 @12:05PM (#48010471)
>People actually made decisions against backwards compatible APIs, intending to cause issues and forcing open-sourcing.

You mean openssl? That said, if we can have /dev/tcp, why we can't have /dev/ssl?

Re:Why TUIs Are Back by skydhash on Sunday May 03, 2026 @07:45PM (#48002834)
> First of all you HAVE to ship the source code if you want it to keep working on every machine because people need to compile it on their machine for it to work, so you're practically forced to open source your desktop app. I know the notion of having a closed source app on Linux sounds weird, but it's more weird that this isn't an option as a side-effect of the how the whole system is designed.

That's so very not true.

Most Linux distros allows for custom repositories. So you can just setup the build infrastructure on your side and then have the users include your repos on their side. No need to open source code and users have painless update notifications.

> It's only on Linux that I feel like the developer is pressured to open source it and make it the user's problem because the system won't provide support.

Lots of users have never seen the source code of their software, they just get the binary package. The pressure you're talking about is imaginary.

Re:Why TUIs Are Back by Pay08 on Monday May 04, 2026 @12:16AM (#48004561)
This is downright misinformation. There are no 100kb Windows programs that work for 20 years. Every single program on Windows ships half of the system libraries again, just for use by itself. Microsoft couldn't be bothered to version their libc at the beginning ffs.
Re:Why TUIs Are Back by GoblinSlayer on Monday May 04, 2026 @12:03PM (#48010445)
I have 161kb program from 1992 and it works. I suspect it doesn't use libc. Well, on windows there's nothing useful in libc anyway.
Re:Why TUIs Are Back by polski-g on Sunday May 03, 2026 @04:33PM (#48001164)
I want to say you could statically link a GUI application, but I'm pretty sure libpthread doesn't cooperate on static linking.
Re:Why TUIs Are Back by badc0ffee on Sunday May 03, 2026 @05:33PM (#48001752)
libpthread is fine with static linking. Where you run into issues is libraries like libresolv that use configuration files in a specific path.
Re:Why TUIs Are Back by cmacleod4 on Monday May 04, 2026 @09:30AM (#48008523)
"worst case is trying to develop some small utility like a tool to search in files using regex" - you mean something like: https://wiki.tcl-lang.org/page/ReacTcl+example%3A+Grv ?

This will run on Windows, Linux, MacOS, and Tcl's starkit/starpack system makes it easy to generate a single executable file for each OS that can just be copied over and run without any installation needed.

Re:Why TUIs Are Back by gray_-_wolf on Sunday May 03, 2026 @04:23PM (#48001042)
I mean, both wxWidgets and Qt are fine, no? GTK 2 and 3 as well (4+ is... meh). There are plenty applications using one of these (often via python bindings).

I think it is more of a staffing problem. Plenty of people know web development, so you want to use those people for desktop as well. Having desktop be JS (electron) helps a lot with that.

Re:Why TUIs Are Back by dpe82 on Sunday May 03, 2026 @04:42PM (#48001262)
A year ago I would have agreed with you, but now anyone can build a perfectly reasonable native app.
Re:Why TUIs Are Back by maccard on Sunday May 03, 2026 @05:48PM (#48001897)
What is native on Linux?
Re:Why TUIs Are Back by Gigachad on Sunday May 03, 2026 @07:46PM (#48002843)
What is native on Windows too. These days the term native app is so confused it's hard to come up with a definition that doesn't include electron.
Re:Why TUIs Are Back by maccard on Monday May 04, 2026 @01:31PM (#48011952)
There’s a few options on windows all of which are native. WPF, Winforms and WinUI are all “native”.

> These days the term native app is so confused it's hard to come up with a definition that doesn't include electron.

Electron is _not_ native.

Re:Why TUIs Are Back by dpe82 on Monday May 04, 2026 @03:08AM (#48005574)
TUIs, apparently. :)
Re:Why TUIs Are Back by mghackerlady on Monday May 04, 2026 @09:47AM (#48008720)
athena[0], take it or leave it

[0]https://en.wikipedia.org/wiki/X_Athena_Widgets