News for hackers. Stuff that matters.

A comment on Ask HN: When do you use a library vs. implement something yourself?. Parent comment

Re:Ask HN: When do you use a library vs. implement something... by eeZah7Ux on Friday April 20, 2018 @04:43AM (#16883179)
> 1. It is still alive

A mature project that just works does not need new commits.

[ Parent | on HN ]
Re:Ask HN: When do you use a library vs. implement something... by bartread on Friday April 20, 2018 @04:54AM (#16883233)
That's true, but whether a project is alive or not goes beyond whether people are committing code. E.g.,

- If you file a bug report does the bug get fixed? Do you even get a response?

- If you ask for help from the community, do you get it?

[ Parent | on HN ]
Re:Ask HN: When do you use a library vs. implement something... by mort96 on Friday April 20, 2018 @04:51AM (#16883217)
True, a project with a bunch of stars and ownloads and whatnot and no open issues and pull requests can be perfectly fine even if the last commit was a few years ago. However, if the last commit was years ago, and issues and pull requests have been piling up without getting any attention, that's probably a bad sign.
[ Parent | on HN ]
Re:Ask HN: When do you use a library vs. implement something... by aetherspawn on Friday April 20, 2018 @07:21PM (#16889103)
You can determine that by ie looking at the issues list and eyeballing whether there are pages of issues with no comments on them.

Not necessarily whether there are commits or not.

[ Parent | on HN ]