Earlier quoted context omitted.
Hm, that's interesting. Maybe it would make more sense describing the way how to choose a module from various alternatives. But what I meant by 'author should care if somebody uses it' is that he should make it usable and understandable for somebody else. If it's not, what the point of making it public and open source?
I have lots of code all over the internet "rotting". Some of it was written because I actually needed it. Some because I was learning. Some to prove a point. Some to just play. There's lots of reason to write code, and lots of reasons to let it go. Now here's the thing, putting code on the internet and typing "here it is, BSD or MIT or whatever licensed" is a trivial marginal effort. Since that effort is effectively…
What makes this worse is that your "rotting" should be written without quotes. Most code rots incredibly fast, even if it is written to high standards. Your makefile may break, your dependencies may see an interface change, popular architectures may change (an .ini file for preferences?), etc.