News for hackers. Stuff that matters.
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