I don't have any technical problem with NodeJS.
My problem with NodeJS is that it practically stopped the progress on the CommonJS discussion group, by moving the attention from important issues like a standard library, module transport, etc to non-issues like async. What a pitty...
Re:RingoJS vs NodeJS
by aaronblohowiak on Wednesday June 23, 2010 @02:28PM
(#1455757)
async is the main reason to use NodeJS, and it supports the older module spec. I'd rather no standard library than a sub-par one.
Ah, yes. You called it a toy because toys are known for disrupting the progress of other projects? That's what toys do, I suppose?
You're backpedaling. If you're going to rant, own it. Otherwise don't rant.
I'd appreciate a couple of observations regarding what you "didn't like at all"; while I don't think that every tool has to cater to every taste or requirement, you are, AFAIK, a long-time (client-side) JavaScript developer, and getting honest feedback from that clientele would be extremely beneficial for the project.
You're not going to like any of my feedback because our views are polar opposites. :)
The OP's advice is sound: Stop making groundless rips on the other tool, and talk about why Ringo is better. Even "better" is totally subjective, because it depends on what you WANT from a tool.
But instead of saying "If you like x, you'll love Ringo!" you basically resorted to telling those of us who love node that we're stupid.
I frankly don't care. I've seen Ringo in action and I looked at the code, and I didn't like it at all. The points you gave it in its favor don't matter to me, either. I think node is vastly superior.
But, I'm not sniping about it in inflammatory blog posts. I just. don't. use. it. That's what you do when you don't like something: you don't use it.
Getting all aggro just makes you look childish, and causes people to ignore your message.