Live data from Hacker News

Why TUIs are back

wiki.alcidesfonseca.com

131–140 of 443 posts

Re: Why TUIs are back

#131

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

FYI this is why I still use Vim sometimes. I am OOM more productive in JetBrains, but sometimes I have to feel like Hiro Protagonist. So, Vim it is.

Re: Why TUIs are back

#132

> 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…

Map to "jj" and call it a day since your finger is already on the home row

Also ctrl + [ is standard terminal/ascii for esc so that might be a bit more ergonomic than reaching for esc

Re: Why TUIs are back

#133
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.

Which is why I never went with CapsLock being both Ctrl and Escape depending of whether it's part of a key combo because it's whole setup. On the contrary, whenever I use someone else's machine I can quickly go in the settings, set the option and then set it off after I am done.

Re: Why TUIs are back

#134

Earlier quoted context omitted.

> 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!

Yeah, I noticed some TUI libraries in npm when I was working on a Typescript project a couple of years back so I'm sure people are doing it.

Re: Why TUIs are back

#135
It's based on trends, momentum and social signaling more than anything, like most things in technology and society. Humans are herd animals.

I am affected by it also and have always been fond of TUIs in a nostalgic way.

Re: Why TUIs are back

#136

> 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…

Map to "jj" and call it a day since your finger is already on the home row Also ctrl + [ is standard terminal/ascii for esc so that might be a bit more ergonomic than reaching for esc

Yes but then you get used to jj (or jk) which might not be available on other vi modes (shells vi modes, gdb, glide browser ?) and it's overall quite nice to quickly escape any situation by having the key be closer.

Ctrl + [ would be acceptable if it wasn't, imo, the most important function of the editor.

EDIT: My bad, you can do it with Glide apparently

Re: Why TUIs are back

#137

> 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…

Map to "jj" and call it a day since your finger is already on the home row Also ctrl + [ is standard terminal/ascii for esc so that might be a bit more ergonomic than reaching for esc

"jk" is even faster (you get to "roll" your fingers)

Re: Why TUIs are back

#139

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.

Claude code is react and their desktop app is Electron. But “coding is largely a solved problem”.
Post reply on HN