The code generated by Claude is fully under my control, and I make sure it works exactly as I intend. I could have hidden this by committing it myself, but I choose to acknowledge that I had Claude's help
It’s not your fault. The problem is now that my mother in law can vibe code a complete operating system, I cannot distinguish quality from shit any more. And the last few OSS projects that I tried that had the Claude icon where shit and breaking in many ways.
It's kinda like eternal September but for software engineering. There was a time that just being on the internet, having an email address, etc. was a signal that indicated a level of technical proficiency. Now everyone has that connectivity, it doesn't mean anything anymore.
A clickable TUI is contrarian to why I use most CLI tools. Neat that they could build this, though, because it suits their needs.
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?
I hope vibecoding doesn't mean the concept of contributing upstream gets lost. At least some of this (mouse clicking) would have been a great upstream contribution instead of rewrite.
I wish we had a "cool" GUI toolkit. GUIs are way better at this stuff. Adding point and click is so close to being a GUI, the only possible reason this is a TUI is fashion.
How are GUIs "way better at this stuff"? I can't see it, but would like to understand how you feel that a GUI can improve on the management of automated processes at scale.
Idk if you are managing k8s stuff you are probably in a terminal already. Staying in a terminal is nice. Plus having persistent multiplexer sessions is a big deal in locked down corporate environments.
Most common things power users seem to want from TUIs on desktop:
- 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 fact. Something like SPICE/QXL but more semantics-aware? Maybe too low level but why not.
- 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!
Or can we do it with a cli wrapper process?
Same concept, but github repos now.
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?
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.
Imgui is also good for this
I appreciate the tui.
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 fact. Something like SPICE/QXL but more semantics-aware? Maybe too low level but why not.
- 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.