-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any new optimizations of V8 #17
Comments
Dart is another language, which has nothing to do with javascript (unless I missed something). FF thingy is being discussed in another thread here. Shortly speaking, it's "would love to see it, but too hard" kind of a deal. |
Dart compiles to JS at the moment since No browser(yet) supports DartVM, but DartVM still performs faster. |
@Ap0ph1s Java VM is even faster. And you also can compile Java to JS |
Haskell compiles to JS as well. So does python. It doesn't mean we're switching to them, does it? This is a JavaScript community, and frankly speaking many people here will prefer Dart only at gunpoint (1, 2, etc.). So unless you can run JavaScript under DartVM faster, there isn't any reason to suggest it. But SpiderMonkey can run JS faster (and better, I'm talking es6 features), so that's a good thing. |
Are you sure? Generators are pretty special and it's a good thing that they are fixed now, but it's frightening to know that using some features can force spidermonkey to run code using interpreter mode. |
No. I would like to stress "better" and "es6" in my reply. But they are roughly the same nowadays. See this blogpost from a month ago where SM overrun V8 on their performance metrics. And here is a nice website: http://arewefastyet.com/ Maybe I'm wrong about "it is faster" in node.js use-case, but "their performance is roughly the same" still applies. |
guys http://www.rust-lang.org/ Ok jokes aside, this belongs on Google's V8 issue tracker, not here. (If you're wonder what version of v8 node 0.12 will drop with, it will probably be 3.30.x I think.) |
DartVM and some FF JS engines are surpassing V8, any optimizations coming this way to turn the tables?
The text was updated successfully, but these errors were encountered: