Link Share / Bookmarklet Module

The functionality was already explained, I even clarified it, but it's obvious the developer was too caught up showing off how she wasn't a part of the facebook 'fad'. If she really couldn't understand (didn't read) the explanationS then she should have googled it, or is google a fad too? In that case, register a dummy account and in 5 minutes you can see it first hand. Either of those options would have been quicker than complaining and waiting for someone to describe it (or having some brown noser post a screencast).

If you're comparing facebook and twitter then you're being ignorant in just the same way. Twitter is great, for some people, to do some things. Facebook is infinitely more successful, and there is a reason. It's because they haven't stopped creating and evolving ideas and features and functions, which has made the site incredibly useful, to the point that it's a necessity, even for people like you.

You can make statements like "Some people don't really need to know that their friend went to see Transformers 2 over the weekend in order to feel connected to them.", and be saluted by all the other try hards who are busy feeling good about being so alternative, but the truth is, that's like saying there's something wrong with the internet, because of all the crap it contains.

The facebook team long ago knew about the potential problems that would arise from such a vast and popular online community, so they went to a lot of effort to provide solutions to those concerns and I'm betting those solutions were implemented long before you even realized you could get some (meaningless) peer approval by blatantly, and under the guise of a real person with a real concern, rejecting something so mainstream.
Facebook's commitment to usability and user experience has produced features like the ability to completely control what is displayed in a users feeds, so they can't complain about having crap forced down their throats OR the privacy controls through which a user can configure their account to any degree of privacy, from broadcasting every event/action to being completely invisible.
Face it, it's a great application/platform, a revolution, incomparable to myspace or twitter, and I think the mere fact that a Drupal developer thinks he/she can s#*t all over it shows the real problem with the Drupal community and Drupal module maintainers, arrogance and ignorance.

Which brings me to maintaining a module for the drupal community.

I consider myself quite familiar with the ins and outs of what it takes to maintain a Drupal module, and according to me, it goes a little something like this...

Fred (the developer) plays around with php a fair bit and obviously enjoys the engineering aspect of programming but can't seem to put it all together into a successful project due to a lack of understanding of the enormity of the whole process (not uncommon or wrong). Then Fred discovers Drupal and is immediately excited by it. After breaching the "I suck" threshold (lame name by the way), Fred is very chuffed with himself and starts calling himself a Drupal developer. So now Fred apparently has all the tools and knowledge he needs to produce some great work, but it still isn't happening. Fred, like so many of us, fears failure and finds some relief in good ol' coding. Then he sees his opportunity. Module development.

Before long he's up to his neck in the development of one or more (more is better) super duper modules which of course he releases for free as a way to give back to the Drupal community. He has a long list of issues submitted by a long list of people who have not yet given up trying to make a successful site out of Drupal (and 10+-, apprently optional, behemoths of modules) without knowing any PHP or JS. This notoriety affords him a sense of worth as a developer which is then supplemented by the feeling he gets from doing it all without being paid. In his mind, he is a giver, and if it ever gets to much, or if anyone ever suggests that he's made a mistake, he can come at them with 'I don't get paid, and I'm very very busy! Check out my issue queue! I'm a saint!" Basically, after all of it, he's unaccountable, and motivated by something completely separate to the needs of the users.

The Drupal community as a whole does a good job of encouraging this. Their stories are similar, and this results in the whole lot of them getting around like they've invented electricity (but forgot to make it usable), constantly patting each other on the back, muttering praises about the community and having endless discussions about the 'extensibility' and 'modularity' of Drupal while ignoring the fact that a huge portion of their user base are simply kids, dreamers and no hopers who will never produce anything of value from Drupal.
As far as I'm concerned, the fundamental flaw of Drupal is the intense focus on modularity and how it aims to be a, somewhat, out of the box solution. Contrib module developers spend so much time/code creating massively bloated modules that integrate with views and cck (and the other "optional" modules) but in the end still require further contrib modules (or hacking) to produce original/correct (situation specific) behavior, i.e. good internet.

Drupal contrib module maintainers satisfy the group of people that will never make anything of their attempts with Drupal, because anyone who wants to do anything serious will either re-engineer all contrib functionality or simply move onto something that isn't so limiting.

Maintainer note: Ad hominem attack deleted.