I never turn down a chance to plug my favourite TUI - jjui, for controlling jj vcs. Life changing combination (and jjui is built with Charm)
Building a TUI is easy now
111–120 of 262 posts
Re: Building a TUI is easy now
#112Re: Building a TUI is easy now
#113TUI: Terminal User Interface
Re: Building a TUI is easy now
#114Alex, It's somewhat ironic that a web page about performant terminal user interfaces uses gratuitously complex CSS mask compositing and cubic gradients which reduce smooth scrolling on my 1 year-old, high-end Dell XPS laptop (>$3k) to Commodore 64 level (on default 'Balanced' battery mode). While it's pretty , it's also just a very subtle, non-critical background animation effect. Not being a CSS guru myself, here's…
FWIW, this page looks just fine in a text-only browser running in textmode, no X11, no Javascript, no CSS, on an old, underpowered computer
Re: Building a TUI is easy now
#115> The Hatchet TUI is not well supported on mobile devices.
Isn't everyone else remoting into a Claude instance on their phones?
Re: Building a TUI is easy now
#116> The Hatchet TUI is not well supported on mobile devices. Isn't everyone else remoting into a Claude instance on their phones?
Primary driver for me (finally) learning tmux.
Re: Building a TUI is easy now
#117Re: Building a TUI is easy now
#118I love Claude Code, but how they made the TUI is just plain stupid. Not how it looks, but you know, the React part.
Re: Building a TUI is easy now
#119I love Claude Code, but how they made the TUI is just plain stupid. Not how it looks, but you know, the React part.
It’s a very cumbersome UI that feels extremely bloated. Especially if you have a lot of text you want to scroll over — eg i want to see the details of the last X exchanges - it just performs absolutely horribly.
It seems like it already was like this from the start, though? I’m not a frontend / TUI dev, but why are these issues so hard to fix?
Re: Building a TUI is easy now
#120Earlier quoted context omitted.
The question is how many decades each user of your software would have to use it in order to offset, through the optimisation it provides, the energy consumption you burned through with LLMs.
Would it be that many? Asked AI to do some rough calculation, and it spit that: Making 50 SOTA AI requests per day ≈ running a 10W LED bulb for about 2.5 hours per day Given I usually have 2-3 lights on all day in the house, that's like 1500 LLM requests per day (which sounds quite more than I do). So even a month worth of requests for building some software doesn't sound that much. Having a local beefy traditional b…
Is that true? Because that's indeed FAR less than I thought. That would definitely make me worry a lot less about energy consumption (not that I would go and consume more but not feeling guilty I guess).