News for hackers. Stuff that matters.
Re:Node.js memory benchmark confirms V8's GC may not be read... by sh1mmer on Wednesday September 29, 2010 @01:05PM (#1740139)
I think your conclusions in the article are fair. I think the title on HN is misleading because it's a quantitive issue.

V8 GC is a well known concern in the Node community, but it's still performing well enough that Node is considerably faster than traditional servers (like Apache). The fact that Ringo is also faster doesn't make V8 "not ready" it just means it could be improved.

If I wanted to be contentious I could suggest that "Hacker News comments confirms that RingoJS may not be ready for developers" because the author likes taking pot shots at other frameworks. But that would be petty, wouldn't it?

Re:Node.js memory benchmark confirms V8's GC may not be read... by hannesw on Wednesday September 29, 2010 @01:49PM (#1740323)
You are right about the title. That "not ready for the server" is a foolish phrase. I'd change it to "not tuned for the server" if I could, but it looks like it's impossible to change that now.
Re:Node.js memory benchmark confirms V8's GC may not be read... by IsaacSchlueter on Wednesday September 29, 2010 @02:29PM (#1740518)
Maybe you could change it to "Not as optimized as Rhino to parse JSON under heavy load."
Re:Node.js memory benchmark confirms V8's GC may not be read... by z92 on Wednesday September 29, 2010 @01:44PM (#1740302)
> The fact that Ringo is also faster doesn't make V8 "not ready" it just means it could be improved

Well said. Most of us fail to realize this simple point until someone points out.