Ziggity – A terminal UI for Git, written in Zig(github.com) |
Ziggity – A terminal UI for Git, written in Zig(github.com) |
And so it's "actually memory safe".
/sarcasm in case not obvious.
With Claude, i find myself reaching for Magit even less.
I would love to use it without gimmicks.
This is AI generated TUI slop made with claude.
I've been seeing a sad trend of these things being built with AI with no care and will be just abandoned in less than a month.
Why should I use this when I can use lazygit which is more popular and has been around and battle tested for years?
Yes, smells like vibe code. Haven't looked inside but can already tell
Is that the principled position you want stand on in 2026 and beyond?
Why another one? Two reasons, honestly. There were a few areas of lazygit I wanted to improve on for my own workflow, and I wanted a real project to build in Zig, which is genuinely powerful and fast, and a joy once it clicks. It compiles to a single small static binary with explicit memory ownership and no libgit2, it just shells out to the `git` you already have. The UI is built on libvaxis. And I let myself add a bit of sugar along the way, because a tool you stare at all day might as well be pleasant.
A few things that are a bit different from lazygit: - A divergence view + status-coloured commit hashes so ahead/behind commits stand out at a glance - Independent drill-downs in the Branches/Commits panels (deliberate, not a port artifact) - Line level staging, interactive rebase, custom patch building, bisect, arbitrary-ref diffing
It's honest about its stage: v0.3.0, macOS/Linux/Windows builds, MIT. The Windows build compiles and libvaxis supports it, but I haven't smoke-tested it on real hardware yet. There's an about screen with a spinning ASCII donut, because why not.
Install: `brew install simoarpe/ziggity/ziggity`, or grab a static binary from the releases page.
Repo: https://github.com/simoarpe/ziggity
I'd genuinely appreciate feedback, especially on the UX and on the Zig code if you're into that. It's a spare time project, so bug reports and "this feels wrong" notes are welcome.
Maybe I've missed some context
Just FYI a large portion is vibecoded for those that don't like that.
So you would use AI including LLM autocomplete at work, but at the same time, you don't want anything to do with it?
You just previously said that:
>> "...If written by agents, I don’t want anything to do with it. I only want human written software, even LLM autocomplete seems a bridge too far."
That means you would still use AI at some capacity which breaks that guarantee.
This also means that you just contradicted yourself, when I explicitly said in any capacity that you would never use AI or agents at all.
> (deliberate, not a port artifact)
Smells like AI
I guess you folks are right and it's probably the llm filter. I looked at the GitHub and thought it had too many screenshots to not have had some human effort, but who knows these days.