Re:What the web platform can learn from Node.js: The Darwini...
by matthewtoast on Thursday December 17, 2015 @08:50AM
(#10751406)
I agree and that's what I like to do too when these issues come up (time permitting). Still, I hope my basic point came through: the small modules approach isn't a panacea; it can add its own set of problems; "monoliths" can be a good choice, not always, but sometimes.
There are several times I've found something close to what I want, I fork it on GH, change the bits I want, update the name everywhere and publish it... many times they continue to work as-is without much grief. Of course that's part of why there are so many options for any problem.
I usually look at the following, when was the last commit, and how many issues have been sitting stale for over a month... if the last commit was several months ago, but there aren't any recent issues, I'll check through the backlog issues.... some libraries reach maturity and don't change much, if the issues aren't recently curated, I move on...