You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They're all good engines. SpiderMonkey is definitely in some aspects while v8 is faster in others. JSC is probably faster in some other aspects.
I doubt that iojs will switch away from v8 because of how tightly integrated it is until, and if, we break it into pieces ( #9 ) but that is off the table for now because it is a major rewrite and requires a lot of time that no one has currently.
It would be, at present, prohibitively time-consuming to switch Node over to a different JavaScript engine -- though it could be approached as a separate project. For more background, there's a bunch of discussion over here.
Activity
gkatsev commentedon Dec 4, 2014
They're all good engines. SpiderMonkey is definitely in some aspects while v8 is faster in others. JSC is probably faster in some other aspects.
I doubt that iojs will switch away from v8 because of how tightly integrated it is until, and if, we break it into pieces ( #9 ) but that is off the table for now because it is a major rewrite and requires a lot of time that no one has currently.
chrisdickinson commentedon Dec 4, 2014
It would be, at present, prohibitively time-consuming to switch Node over to a different JavaScript engine -- though it could be approached as a separate project. For more background, there's a bunch of discussion over here.
napi: Error handling tests and fixes (V8) (nodejs#72)
deps: V8: cherry-pick 254c7945eea2
deps: V8: cherry-pick 254c7945eea2