[greggroth]

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?

[arjie]

In general, for most projects like this the README is the product. You usually have better results using it and the code as a starter prompt for your own software if you feel the need. I wouldn’t use this kind of thing directly from upstream.

[TheSorcerer]

This is probably the most valuable feedback received so far. I'll make sure to draft a new README file following what you have suggested. The current version was partially written with the help of AI as English is not my primary language but I recognize that I should put more emphasis on what this project solves. I've put a few points in a separate file called ENHANCEMENTS_OVER_LAZYGIT.md but I will probably review and merge it into the primary README file. Thanks!

[oldmoozy]

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.

[TheSorcerer]

"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.

[oldmoozy]

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!

[tosti]

If this is idiomatic zig, functions must be expensive because it fails horribly in the DRY departement. Also, papering over exceptions everywhere by... catching and not handling exceptions. What could possibly go wrong?

[blueaquilae]

You have no idea don't you? it's like telling Ghostty failed because you don't understand how try/catch was a mistake in software conception.

[dwattttt]

Why are there exceptions in the first place then? If that's what you want, write ON ERROR RESUME NEXT and be honest about it.