Let me preface this with the fact that I am a huge Node.js/V8 fan and have actually written an FFI interface for Node.js (that shamefully needs some updating). I am also a huge Ruby on Rails fan, so I'm not some kind of performance-obsessed VLIW-assembly-coding uber-nerd.
I had a feeling I'd get down-moded for questioning "de jour" on HN. Let's deconstruct this hyperbole. Ultra is a prefix from Latin that means "beyond." Is it really BEYOND high performance?
Frameworks like Django and Rails focus on features and ease of use over performance. They are not high performance, they are high productivity. I truly believe that the developers of this new framework are focused on high performance, but they are still relying on an VM environment that is still 1/3rd to 1/5th the performance of C. How is this going beyond high performance?
I suppose all of this is nitpicking someone's marketing speak, but let's get real about what performance is. It would be nice to be spoken to by other engineers like an adult with a brain, instead of bullshit like "ultra high performance." This is the irrational kind of stuff that causes framework and language holy wars.
"SQL is slow."
"Rails can't scale."
"Dynamic languages can never be fast."
"Java uses up all your memory."
Bravo, this type of hyperbole has made non-expert comparisons impossible in so many other industries, let's try and prevent it from completely encompassing computer science.
haha :) touche` pardon my crappy use of the english language. I will replace my lame use of "ultra high performance" with "Focused on high performance" as that is the end goal of course.
That being said of course it will never be as fast as C[++] or erlang that is just a given
I had a feeling I'd get down-moded for questioning "de jour" on HN. Let's deconstruct this hyperbole. Ultra is a prefix from Latin that means "beyond." Is it really BEYOND high performance?
Frameworks like Django and Rails focus on features and ease of use over performance. They are not high performance, they are high productivity. I truly believe that the developers of this new framework are focused on high performance, but they are still relying on an VM environment that is still 1/3rd to 1/5th the performance of C. How is this going beyond high performance?
I suppose all of this is nitpicking someone's marketing speak, but let's get real about what performance is. It would be nice to be spoken to by other engineers like an adult with a brain, instead of bullshit like "ultra high performance." This is the irrational kind of stuff that causes framework and language holy wars.
"SQL is slow." "Rails can't scale." "Dynamic languages can never be fast." "Java uses up all your memory."