I'm fine with K9s and lazygit key-driven interfaces.
I guess one thing that's good about a clickable TUI is that maybe it's easier to approach for some, wihtout releasing yet another memory hog Electron App?
Claude code uses react, iirc
We’ve had low quality code for as long as we’ve had programmable machines. I’ve seen a lot of manually written bad code well before LLMs took over. Nowadays, I primarily look at how long a repo has been around and how active it is. A repo that has consistent activity is probably going to be a higher quality one. Even better if I can follow PRs to see how the code base is evolving.
I will admit it’s become more difficult to tell low quality git repos from higher quality ones. Missing files or incomplete README files are a thing of the past. Claude is very good at filling in the gaps to make all repos at least appear respectable.
Same concept, but github repos now.
But now other people's code is just a starting point for me forking an app to do exactly what I want it to - it's inspiration because code is cheap.
Of course for larger projects we will still need solid components underlying them, but what you're really talking about is just maturity - it's very easy to produce a lot of output now but you can't replace actual history or having more then exactly 1 maintainer.
Why is this a good thing? Have a help you your access via ? and document what the keys are. Don't dumb the interface down.
https://github.com/nklmilojevic/sofka
That's the actual k9s successor imho!
It seems we cannot move on from them and I think we should.
It is a shame because surely there must be something better than terminals and TUIs.
TUIs can have GUI like affordances UX/UI wise regardless of if they use the terminal as the contract or a window server/gui lib
I appreciate the tui.
Imgui is also good for this
we need more experiments with X11 interfaces
- Easy efficient remote access. Pixel streaming and things like GTK Broadway are out. Needs a proper protocol/standard that would send styling-neutral primitives (and that is not X11 forwarding), and the entire toolkit architecture built around that. Something like SPICE/QXL but more semantics-aware? Not sure, might be too low level and chatty.
- Staying in the terminal. This is a matter of window management, though a toolkit can offer good defaults so this doesn't feel janky.
- Keyboard-first. Trivial. "GUI is for filthy mouse casuals" is a ludicrous idea.
- Low bloat. Web and things like GTK Broadway are out.
I haven't seen two similar opinions on actual architecture and stack, however being available in Rust will be a great start.
When Claude added it, I immediately hated it since you click into the terminal and accidentally click something.
I don't mind something that requires a modifier key like Shift+click to follow a URL
But so many times now I'll click to get focus and now that's selected some option or opened some pane.
If I wanted that, I'd use the Claude Desktop app!
Unfortunately, of the popular DE's, this is only supported in Xfce (?), and it's not supported in Windows or macOS afaik.
There are reasons for both - but ignorance shouldn't be one.
https://9p.io/wiki/plan9/Using_acme/index.html
Or can we do it with a cli wrapper process?
Actually, I’d really like to know the answer to this. I’m not a fan of clickable TUIs. Mouse events in my terminal are one of the banes of my existence.
But, if they are more popular with others, that would be helpful to know.