JavaScript Engines

JavaScript Engines

Vidja Games — Page [1]
sprinkles

Chrome Whore
2009 Sep 6 • 2547
10 ₧
So as of now Google Chrome has the fastest JS engine. Opera announced that they are making the "next-gen" fastest JS engine (it performed 2.5x faster than the one in Presto 2.2). And Mozilla claims to have boosted their JS engine.

I am curious to see who is going to have the fastest JS engine.
I am not going to bank on FireFox. Personally, my money is on Opera, simply because Google's V8 is years old now. To me Firefox has always been more robust than fast. Chrome is the fastest, and Opera is wonky (I blame it Presto).

I am also curious about the next-gen layout engines, but it seems everybody's attention it on the JS engines right now.
 
 
2010 Apr 3 at 14:38 PDT — Ed. 2010 Apr 3 at 14:39 PDT
Down Rodeo
Cap'n Moth of the Firehouse

Find the Hole II Participation Medal
2007 Oct 19 • 5485
57,583 ₧
It's interesting actually, I was reading a post by the Firefox developers about their JS engine... essentially Spidermonkey, or whatever this one's called, is shit hot at loops but has problems with branching because it doesn't run branched code through the JIT. Loops do however. I don't like Opera, I feel they bring very little as compared to the other browsers - they're essentially a closed-source alternative to IE which don't sit right with me. Same reason I'm not fond of Safari, but it's based on Webkit, maybe?

So yes, the Firefox engine, it's going to be improved soon to deal better with branching code.
 
 
2010 Apr 3 at 15:05 PDT — Ed. 2010 Apr 3 at 15:16 PDT
SuperJer
Websiteman

2005 Mar 20 • 5998
The only one I'm at all familiar with is V8, and it seems that it won't be possible to get a lot faster than that. It compiles to your native machine code so unless they made some huge mistakes, it's already at the speed limit, or close to it.
 
 
2010 Apr 3 at 16:58 PDT
Down Rodeo
Cap'n Moth of the Firehouse

Find the Hole II Participation Medal
2007 Oct 19 • 5485
57,583 ₧
SJ - I think it's the code they choose to compile that determines how fast it can go. If V8 compiles everything for large JS files that'll take a while; comparatively doing very little means the whole code runs slowly. Of course this is the idea behind what I was saying earlier, with the compilation of loops. I suppose it's like putting assembly in critical loops in other code.
 
 
2010 Apr 3 at 17:23 PDT
sprinkles

Chrome Whore
2009 Sep 6 • 2547
10 ₧
Well the basis of V8 is that it doesn't compile everything into native machine language. It only compiles variables that are used more then once. I cannot remember it all, because I watched it then went on a hike, so it completely escapes me.
 
 
2010 Apr 3 at 18:21 PDT
Down Rodeo
Cap'n Moth of the Firehouse

Find the Hole II Participation Medal
2007 Oct 19 • 5485
57,583 ₧
I see - so we have some funky different approaches... Personally, I think ECMA script is horrible anyway.
 
 
2010 Apr 3 at 18:26 PDT
sprinkles

Chrome Whore
2009 Sep 6 • 2547
10 ₧
I am going to watch the video again tonight.

Right now I am going to watch a webinar on the newest InstallSheild.


No I am not. They couldn't even get an English speaking person for the webinar, damn Arabs.
 
 
2010 Apr 3 at 18:30 PDT — Ed. 2010 Apr 3 at 18:43 PDT
sprinkles

Chrome Whore
2009 Sep 6 • 2547
10 ₧
Here is the V8 engine vid


Sick vid

 
 
2010 Apr 3 at 19:44 PDT
Page [1]