I fucking hate you all. All of you equally. :) | Hacker News Reader

I fucking hate you all. All of you equally. :)

su-shee.tumblr.com

11 pointsMithaldu13 comments

Open articleView on HN

I'm sure i'm missing some important context because some other folks liked this post, but it ends up coming off as entitled whining.

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.

The context you're missing is that this is basically a comparison between different languages that points out how all of them fall short. The message is not "I expect this.", it is "That language does that correctly, why can't you?"

except is it? are most 0.1 module 'maintainers' responsible to the OP for high code quality, impeccable documentation and ease of integration?

If this post is a language gripe, then at least argue about language peculiarities, not the quality of the open source community's efforts. I would rather read a post arguing that the dream of py3k's never materialize (with examples) than a screed directed towards open source devs that just aren't doing enough.

Let me quote Matt S. Trout:

"UNIX is my IDE. perl5 is my VM. CPAN is my language."

This kind of thinking pervades the Perl community and as such people in it look at other languages taking into account their entire eco system and community. Way too many people seem to think that the turing completeness of a language is all it needs and that all the things surrounding the language are irrelevant, while they in reality often affect massively how quickly something can be implemented.

> are most 0.1 module 'maintainers' responsible to the OP for high code quality, impeccable documentation and ease of integration?

Also, well, yes. On CPAN that is the general feeling. To give an example, here's a module i released, which i never needed to modify beyond the first release and which does a minimal task. Yet it has full docs: https://metacpan.org/module/Win32::Detached

Not sure how this piece-of-shit article got voted up to first page.

The time taken to write it could have been used to improve documentation, help "pip", or package a v0.2 for any one of the modules mentioned.

But instead we got yet-another-rant™ that isn't worth the characters it is composed of.

Ah but see, the writer would need to have enough skills to improve documentation, help "pip" or package a v0.2 for any of the modules mentioned... Had he had such skills in the first place, he would be as frustrated as it seems in the article.

Wanna play "Fallacies Bingo"? :)

https://dl.dropbox.com/u/10190786/fallacies.jpg

Not defending the article here but most of the comments so far are along the lines of "only contributors may complain." Instead of just being silly by only saying that, please tell us why you object to the points made in the article as a few have done.

That's the only way a decent conversation can happen.

Thank you. That is the kind of conversation i hoped for when i posted the link to that blog post.

"SO" this dude uses other programmers code that they chose to submit to the repositories and complain it didn't meet his "high" standards? no docs? write the "fuckin'" docs! or better the source code is there look at it, if the source code is not commented well enough and the way the classes methods aren't clear on how they function then it's probably a bad or hard to maintain module anyways and you are better off not using it! and as others do, i wonder how did this get to the front page.

edit : spelling.

Well, the lack of documentation for NPM modules is kinda disconcerting...but other than that this was a waste of my time. :|

Why is this chlidish article upvoted? This sounds like moaning from a 7th grade kid who just learned Javascript.

TL;DR: everything except Perl sucks, and Perl sucks but only because it's not marketed as well as node. When actually (per the author) it's better.

Reply on news.ycombinator.com