3 ms·

"Libraries and frameworks rarely tell you when they’re buggy messes." GitHub Issues usually gives you a good insight, into what problems exists and whether the

"Libraries and frameworks rarely tell you when they’re buggy messes." GitHub Issues usually gives you a good insight, into what problems exists and whether they get fixed, or not. (as a senior, you likely know, but others reading this, maybe not)

josephg 3y ago
True, though figuring out community sentiment from GitHub issues is a bit tricky. The numbers alone certainly aren’t a good indication because projects attract a lot more issues when they’re popular.
- hutzlibu 3y ago
  Yes, you will have to read the issues. Some are just from people asking for support. Some are obscure issues. Some are genuine.
- tough 3y ago
  Well there's nothing worse than a dead Github with no issues/PR's, unless the software is complete and only bug fixing.
xmcqdpt2 3y ago
Github Issues is full of confounding factors though. Lots of Issues mean that there are bugs but all software has bugs. It also means that there lots of users and that users feel that raising an issue is a good way to get something fixed, which is good! IMO the better metric is how many outstanding unmerged pull requests exist. If there are too many this means that bugs exists and they aren't getting fixed.
- hutzlibu 3y ago
  I did not say the quantity of issues matters. And people can do lots of weird PRs that do not get accepted as well. Code quality, obscure features implemented, etc. but it can be hard to figure out what is what, so they might just sit there open for some time, that is not ideal, but can still mean the code base is solid. For me this is easier to figure out in the issues/discussion page. (And reading the actual source and documentation)