Live data from Hacker News

Ziggity – A terminal UI for Git, written in Zig

github.com

71–76 of 76 posts

Re: Ziggity – A terminal UI for Git, written in Zig

#71

Earlier quoted context omitted.

I started using lazygit a couple years ago, never looked back. It’s great

I've used Lazygit daily for almost four years. It's a fantastic project, and I suggest donating to Jesse as he did a great job. In my daily job a heavily use Git and a few things bothered me, so I decided to create my own project. Go is not a language I wanted to explore, while I had this interest in giving Zig a try, so eventually I picked it and was blown away by how fast it can be. There's a file called ENHANCEMEN…

thanks for the info; will give it a try

fyi, a couple of features that lazygit does not have, or that aren't easily done in lazygit and which pycharm does quite well (I've used _many_ git tools, and IMO pycharm's internal implementation is still the best, but I switched to lazygit because I dropped pycharm for zed).

- diff any branch against any other branch (lazygit relies on certain branches being marked or inferred as main branches against which you can diff)

- see a file's git history (and which branches those commits are on), drill into the commits

- github (or gitlab, codeberg, etc.) support: open commit in github (easiest way to share commit with a co-worker, for example)

Re: Ziggity – A terminal UI for Git, written in Zig

#72

Earlier quoted context omitted.

I've used Lazygit daily for almost four years. It's a fantastic project, and I suggest donating to Jesse as he did a great job. In my daily job a heavily use Git and a few things bothered me, so I decided to create my own project. Go is not a language I wanted to explore, while I had this interest in giving Zig a try, so eventually I picked it and was blown away by how fast it can be. There's a file called ENHANCEMEN…

thanks for the info; will give it a try fyi, a couple of features that lazygit does not have, or that aren't easily done in lazygit and which pycharm does quite well (I've used _many_ git tools, and IMO pycharm's internal implementation is still the best, but I switched to lazygit because I dropped pycharm for zed). - diff any branch against any other branch (lazygit relies on certain branches being marked or inferre…

Thanks! Super valuable feedback! I'll make sure to implement these features in the near future. The branch diff is already there and works quite nice.

Re: Ziggity – A terminal UI for Git, written in Zig

#73

Earlier quoted context omitted.

thanks for the info; will give it a try fyi, a couple of features that lazygit does not have, or that aren't easily done in lazygit and which pycharm does quite well (I've used _many_ git tools, and IMO pycharm's internal implementation is still the best, but I switched to lazygit because I dropped pycharm for zed). - diff any branch against any other branch (lazygit relies on certain branches being marked or inferre…

Thanks! Super valuable feedback! I'll make sure to implement these features in the near future. The branch diff is already there and works quite nice.

another feature that pycharm has (and Zed though not as well implemented): insert the filename into the commit text.

zed inserts the filename but doesn't allow you to edit the commit (so it's all or nothing), pycharm allows you to edit the commit prepopulated with the filename if only one file is staged.

another enhancement is that neither pycharm or zed can handle inserting multiple filenames into the commit. so while editing the commit, you could potentially have keys to insert the staged filenames, i.e., by pressing a meta+number key combo where ctrl+1 inserts the first filename in the staged list, ctrl+2 the second, 1-9. just an idea.

Re: Ziggity – A terminal UI for Git, written in Zig

#74

Neat project, but the README would benefit from a human author. I can tell what you prompted by the way the README is worded. It should tell me more about what this project solves. I don't care that it uses idiomatic zig. Why should I use this instead of lazygit?

Yes, from the README, it's not clear why the author would maintain a project with main features being saving 10Mb of ram&storage and 10ms startup time... followed by a wall of hard-to-read AI-generated text.

Re: Ziggity – A terminal UI for Git, written in Zig

#75

Neat project, but the README would benefit from a human author. I can tell what you prompted by the way the README is worded. It should tell me more about what this project solves. I don't care that it uses idiomatic zig. Why should I use this instead of lazygit?

Yes, from the README, it's not clear why the author would maintain a project with main features being saving 10Mb of ram&storage and 10ms startup time... followed by a wall of hard-to-read AI-generated text.

"Why maintain it" is easy: I use it every day and it's faster than the alternatives.

If the docs are hard to read, PRs are welcome. But if "a wall of text" is the strongest critique here, the code's probably fine.

Re: Ziggity – A terminal UI for Git, written in Zig

#76

Earlier quoted context omitted.

Yes, from the README, it's not clear why the author would maintain a project with main features being saving 10Mb of ram&storage and 10ms startup time... followed by a wall of hard-to-read AI-generated text.

"Why maintain it" is easy: I use it every day and it's faster than the alternatives. If the docs are hard to read, PRs are welcome. But if "a wall of text" is the strongest critique here, the code's probably fine.

To restate my initial point, I don't think the speed is important for tools like `lazygit`. Even on the huge company-wide monorepos it's not a problem, as there are other ways to handle it. For now, you're selling Ziggity to the Zig bros.

> But if "a wall of text" is the strongest critique here

Well, it is a blocker, since you haven't convinced me to try it. The only feature I find useful is the text selection, and to find it I had to dig through the "wall of text".

You have 10s to tell me what my pain point is and how you solve it, before I move on. I understand you're proud of the speed gains. But as a potential (typical) customer, I'm telling you it's not the problem I have.

Anyways, good luck with your project!

Post reply on HN