4 ms·

I think the editorializing of the headline is unnecessarily negative (read biased). There is obviously an issue Ryan is working on addressing but Node is clearl

by sh1mmer 16y ago

I think the editorializing of the headline is unnecessarily negative (read biased). There is obviously an issue Ryan is working on addressing but Node is clearly already providing performance which is suitable for many server workloads.

pthrasher 16y ago
Agreed, node is very fast.
hannesw 16y ago
I'm the author of both the original article and this HN posting - and yes, I am biased, since I'm the main developer of RingoJS (the other platform in that benchmark). I've made that quite clear and provided additional background in the original benchmark to which this is just a short update: http://hns.github.com/2010/09/21/benchmark.html http://hns.github.com/2010/09/21/benchmark.html I think my benchmark and the conclusions I draw from it (after a lot of thinking) are fair. My intention is just to make people see there's no magic bullet with performance or scalability, and that there are alternatives for server-side JavaScript.
- sh1mmer 16y ago
  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?
  - z92 16y ago
    > 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.
  - hannesw 16y ago
    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.
    - IsaacSchlueter 16y ago
      Maybe you could change it to "Not as optimized as Rhino to parse JSON under heavy load."
xearl 16y ago
I think the main point of this post (and also the edited headline) is that this is not an issue of Node per se, but rather of V8.
- tlrobinson 16y ago
  Yeah, but if you mention Node.js in the title of a Hacker News post you're all but guaranteed to get on the front page.

by sh1mmer 16y ago

pthrasher 16y ago

Agreed, node is very fast.

hannesw 16y ago

I'm the author of both the original article and this HN posting - and yes, I am biased, since I'm the main developer of RingoJS (the other platform in that benchmark). I've made that quite clear and provided additional background in the original benchmark to which this is just a short update: http://hns.github.com/2010/09/21/benchmark.html http://hns.github.com/2010/09/21/benchmark.html I think my benchmark and the conclusions I draw from it (after a lot of thinking) are fair. My intention is just to make people see there's no magic bullet with performance or scalability, and that there are alternatives for server-side JavaScript.

sh1mmer 16y ago
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?
- z92 16y ago
  > 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.
- hannesw 16y ago
  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.
  - IsaacSchlueter 16y ago
    Maybe you could change it to "Not as optimized as Rhino to parse JSON under heavy load."

xearl 16y ago

I think the main point of this post (and also the edited headline) is that this is not an issue of Node per se, but rather of V8.

tlrobinson 16y ago
Yeah, but if you mention Node.js in the title of a Hacker News post you're all but guaranteed to get on the front page.