| ▲ | greggroth 21 hours ago | ||||||||||||||||
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? | |||||||||||||||||
| ▲ | TheSorcerer 4 hours ago | parent | next [-] | ||||||||||||||||
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! | |||||||||||||||||
| ▲ | arjie 20 hours ago | parent | prev | next [-] | ||||||||||||||||
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. | |||||||||||||||||
| ▲ | tosti 21 hours ago | parent | prev [-] | ||||||||||||||||
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? | |||||||||||||||||
| |||||||||||||||||