Live data from Hacker News

Why TUIs are back

wiki.alcidesfonseca.com

101–110 of 443 posts

Re: Why TUIs are back

#101
post #70
post #46

Earlier quoted context omitted.

Unfortunately, remapping escape to caps lock can lead to serious friction if you have to work with different laptops a lot, like I do. The muscle memory gets in the way a lot.

If only keyboard makers would just always put escape there.

It should always be "hold for control" and "tap for esc".

Re: Why TUIs are back

#102
Because now we have a young generation nostalgic of their parents experience in the 1980-90's, and that includes the TUI experiences we were stuck with back in the day.

Re: Why TUIs are back

#104
post #46

> The hardcore, moved to vim or emacs, trading immediate feedback and higher usability for the steepest learning curve I’ve seen The only hard part about vim is to be forced to strecth the finger up to Escape for what is essentially the most essential function in a modal editor: Going back to command mode. The ideal workflow is do a quick edit and go back to command ("normal") mode instantly. The fact that Escape is…

Unfortunately, remapping escape to caps lock can lead to serious friction if you have to work with different laptops a lot, like I do. The muscle memory gets in the way a lot.

I always remap Caps Lock to Ctrl. I understand that Caps Lock needed to be next to Shift in typewriters, but in computers it seems like it is wasting a key in the home row for only be used sometimes for screaming (which can be done by holding shift...)

Re: Why TUIs are back

#105
post #60

I think the come back is completely driven by Claude Code. Claude Code is a TUI, Claude Code is successful, therefore let's make everything a TUI! I'm pretty sure the success has nothing to do with the TUI though. I personally enjoy it a lot but the productivity boast doesn't come from avoiding the mouse.

I think TUIs have started to become popular again a few years ago, before Claude Code was released?

Re: Why TUIs are back

#106
The only reason CLIs and TUIs "came back" is because we're still in the early stages of this paradigm, things are moving fast and building a strong GUI UX takes just as much time as building out the backend functionality. So CLI and TUIs are used because they save time, skips the need for building a time consuming GUI. Also building UI is hard.

Re: Why TUIs are back

#107
They are back because modern languages (Rust, Go) have made it pretty straight forward to build them. Ratatui and such allow you to write a TUI really quickly without needing to deal with VT100 arcana.

Re: Why TUIs are back

#108

I think part of it is also that we're able to still LARP as full developers of complex systems while vibe coding by seeing an interface that makes us look like l33t h4xx0rs even though we're just pressing continue 15 times

> look like l33t h4xx0rs even though we're just pressing continue 15 times I feel seen. I also think there’s a certain element of reacting against absolutely everything becoming a bloated electron app. I have no doubt - if it hasn’t already happened - that some apps will unironically embrace the most ridiculous option by shipping as electron apps that implement a TUI layer as their front-end.

> shipping as electron apps that implement a TUI layer as their front-end

A significant number of these apps are nodejs apps so it’s not that much of a leap!

Re: Why TUIs are back

#109

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.

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.

A year ago I would have agreed with you, but now anyone can build a perfectly reasonable native app.
Post reply on HN