17 ms·

I think the problem is that it completely halts development of anything that uses a module that uses underscore (or even a module that uses a module that uses u

I think the problem is that it completely halts development of anything that uses a module that uses underscore (or even a module that uses a module that uses underscore, ad infinitum) since many modules have their dependencies written in such a way that npm will install 1.7, despite it not being compatible. This seems important enough to be something of a public-shaming. edit: Please comment saying why you disagree, rather than simply downvoting.

gojomo 12y ago
"Public shaming" of someone who's been as productive and generous with his open-source work as Ashkenas is never appropriate. Respectfully disagree on the particulars, sure, but don't imply that someone who's given you a gift now owes you extra work, when their own design sense – the same thing that created the shared bounty – guides them otherwise. People should also consider that authors of popular projects are inundated with support requests and demands for their time, and have to set some boundaries on their efforts, which may appear callous to outsiders. If his boundary here is not wanting to embrace Semantic Versioning, respect it, and fork/migrate/workaround rather than whine/shame/guilt.