3 ms·
I do the exact same. However I put more weight on the number of issues a project has. If there are a lot of stars but not many issues, that could indicate a pr
by Chilinot 8y ago
I do the exact same.
However I put more weight on the number of issues a project has. If there are a lot of stars but not many issues, that could indicate a project that isn't really used that widely, or actively.
However, if it has a lot of issues that means it's a popular project with a lot of users that are actively working on making it better.
- continuational 8y agoCouldn’t it also mean that the code quality is poor?
- toasterlovin 8y agoIt certainly can. But that's where digging into the issues comes in. You can learn a ton about a project by seeing what kind of issues pop up and the discussion around issues.
- geofft 8y agoIssues are used as often for feature requests and potential improvements as for bugs, so a high number of issues is not a strong indicator of poor quality. (Also, people usually look at existing issues, so a common bug only shows up as a small number of issues.)