Node, Twitter, and Apologies

I'm gonna copy what I said in the other thread, because it's more relevant now:

You know, reading the various devs' tweets, they use twitter in a way that is completely foreign to me. Is there anything these guys think that they don't tweet? ("Hey, who's picking me up from the hotel?" is not something I'd ever announce to the world at large.)

This incident shows a danger of working that way--one of these guys apparently had a rude little thought best kept private--and let's admit it, we all have those thoughts at one time or another. But because he tweets everything, that little passing thought was pushed to the world, which is not good for anyone involved.

I would like to see someone respond to a twitter message called out (like the one in question) and give a real apology. If you are truly apologetic for the tone but not the substance, use the apology as an opportunity to say as much! It offends our sensibilities to see a half assed apology that completely misses the point. If you think the tool is unnecessary, say why! Give a coherent argument and then we can have a discussion. Otherwise it comes off as phony.

Node inherits the warts of Javascript. Node the framework is quite good and handles abstracting out threading/async incredibly well.

Node the community is still young, but growing. On two recent projects, I tried two different http auth related modules (digest auth). Both had been active for awhile and recently updated (within a month or two). Yet, despite digest auth being pretty established/spec'd out, had some serious flaws (I didn't have the time to offer back feedback, but it is on my list to submit patches). Friends have mentioned similar, though more complicated issues w/ socket.io for production use, one of THE modules used to highlight Node.

Node, JS, and the node environment have their warts, just approach them knowing that. Don't advocate them as awesome rockstar tech.

It often happens. E.g., when you are starting a new project on your current infrastructure. Which is where most new projects happen.

Because javascript has a number of serious flaws.

And because when you bolt everything back on to node to get a decent webdev environment it's really not that fast.

And because callbacks are a really shitty way to write async code.

Like most things node is a tool with a very specific use case, as is typical with anything that is particularly fast at one task people assume that it's fast at all tasks. (C anyone?)

And also because unless you are running a free service your code really has to be absymally slow to not make money. Therefore you should program in the environment that is most pleasurable rather than the environment that is 'fastest', whatever that means.

But mostly because most of the people who talk about how great node is really don't have a clue what it actually excels at. Basically, for all the same reasons people hate PHP.