To summarize the author's gripes:
> Why are there modules in 2013 which aren’t pip’ed? > You don’t just drop version 0.1 and never care for it again. > I really want good documentation and examples.
talk about looking a gift horse in the mouth. there was an insightful post on here a while back about how repo-owners should give write access to (most) anyone that submits a pull request. That seems like a better solution than complaining about half-baked modules.
tip for the author: fork, update and pull request. Even if your changeset isn't accepted, it will probably help somebody in your position.
> I expect from a general purpose language a broad, general purpose range of useful modules. > I expect a certain pacemaking and modernity, a friendly competition between languages and interesting features.
the whole post is a series of moving goalposts. 'i hate perl because it's not java,' 'i hate js and ruby because they lack a comprehensive package database like perl,' 'i hate python because i have to manually run setup.py like a chump,' 'i hate perl because it's too complex,' 'i hate every js and ruby project because they don't have docs,' 'i hate java because it's stodgy and enterprisey'
Instead of looking at these as obstacles, why not approach any of these issues as opportunities instead? That seems like what happened with the python Requests module. The author complains about the lack of general purpose modules in npm (which, huh?) and then bemoans only having web frameworks to hack on.
i'll grant that sometimes it feels like everything sucks, but that doesn't mean we shouldn't do something about it.