Re:Asm.js: The JavaScript Compile Target
by falcolas on Wednesday April 03, 2013 @01:26PM
(#5487496)
... in an optimized fashion. Being valid JS, V8 could run Asm.js code.
[ Parent
| on HN ]
Which doesn't matter in this case, as this fact doesn't give any incentive to Node folks to use it in V8.
Re:Asm.js: The JavaScript Compile Target
by falcolas on Wednesday April 03, 2013 @05:07PM
(#5489076)
Not yet, but if Chrome takes the route of optimizing the asm.js subset of javascript, node.js could gain a lot of traction as a generic high performance asynchronous platform.
And that may just be worth getting excited for.
NodeJS is already gaining traction as a high performance asynchronous platform... Though it's best fit has been in situations that are more IO bound than CPU bound, where it's been a bad fit. This could make it a better fit for CPU tasks, with high IO.
Right now, I have a few workers managed in node, that run compiled code. It works pretty well, but having more of that as modules directly available in Node, with nearly the same performance would be really compelling.
Not needing to compile certain NodeJS modules is what I'd find really compelling.