I was recently excited to find out that V8 is starting work on adding
generators support. Then I heard about asm.js and looked into Firefox's
*Monkey (OdinMonkey, SpiderMonkey, etc.) series of JS engines. Performance
is good, they've already implemented many ECMAScript 6 features, and now
On Wed, Apr 3, 2013 at 4:08 PM, cpprototypes cpprototy...@gmail.com wrote:
Looking at all this, it feels like V8 is falling behind and stagnant.
Also Google is working on Dart which is a competitor to JS technologies.
Mozilla seems to be all in on JS tech instead of divided like Google.
I
I think this might be of interest:
https://github.com/creationix/luvmonkey
quoting:
This project is an effort to create a custom SpiderMonkey runtime that
has libuv built-in. This will give it very node.js-like semantics, but
using a different JavaScript engine.
2013/4/3 cpprototypes
I would love to see luvmonkey finished. Once the core spidermonkey -
libuv bindings were complete, the rest could be implemented in pure JS on
top. Someone could clone the node.js APIs in pure JS on top of luvmonkey.
From what I know about node's development, changing engines will never
happen
Yep. Native node modules use V8 calls directly, so any existing native bindings
would need to be rewritten.
On Wednesday, 3 April, 2013 at 1:55 PM, Tim Caswell wrote:
I would love to see luvmonkey finished. Once the core spidermonkey - libuv
bindings were complete, the rest could be
On Wed, Apr 3, 2013 at 10:55 PM, Tim Caswell t...@creationix.com wrote:
I would love to see luvmonkey finished. Once the core spidermonkey -
libuv bindings were complete, the rest could be implemented in pure JS on
top. Someone could clone the node.js APIs in pure JS on top of luvmonkey.
Suppose you build a node clone with mozilla js engine and you can use
asm.js, would that, to some extend, reduce the need of native addons?
Ps: +1 on kickstarter.
El 03/04/2013 21:23, Stephen Belanger cyruzdr...@gmail.com escribió:
To Kickstarter! :O
On 3 Apr 2013 17:12, Ben Noordhuis
