Linked by Thom Holwerda on Fri 10th Sep 2010 15:06 UTC, submitted by lemur2
Mozilla & Gecko clones "Mozilla has published the first Firefox build that integrates a new JavaScript engine that aims to match the performance in IE9 and reduces the gap to Safari, Opera and Chrome. The JavaScript performance is pretty dramatic and, at least on our test system, Firefox 4 is now faster than IE9 PP4."
Thread beginning with comment 440602
To view parent comment, click here.
To read all comments associated with this story, please click here.
Gusar
Member since:
2010-07-16

Jaegermonkey is NOT older than two weeks. The very first build of Jaegermonkey was August 31, 2010. Before then Mozilla had two separate javascript engines in development, neither of which were Jaegermonkey. One was Tracemonkey, and the other was Mozilla's new JIT engine.

You've got your terminology confused. The "new JIT eingine" *is* JaegerMonkey. And just btw, TraceMonkey uses JIT too. It's just that TM is tracing JIT, while JM is method JIT.

JaegerMonkey has been in development for at least three months, possibly more. It's just that it was developed in a branch. Then, on August 31st, it has been merged from it's own branch into the TraceMonkey branch. And yesterday, the now combined JM+TM have been merged into mozilla-central, which is the "trunk".

Oh, and let's throw another word into the mix: SpiderMonkey. What is SM? Well, it's Mozilla's JS engine as a whole. In the beginning, there was SM, an interpreter JS engine. Then, TM was added to it. And now JM too. So SpiderMonkey now consists of an interpreter, a tracing JIT engine and a method JIT engine.

Reply Parent Score: 1

lemur2 Member since:
2007-02-17

You've got your terminology confused. The "new JIT eingine" *is* JaegerMonkey. And just btw, TraceMonkey uses JIT too. It's just that TM is tracing JIT, while JM is method JIT. JaegerMonkey has been in development for at least three months, possibly more. It's just that it was developed in a branch. Then, on August 31st, it has been merged from it's own branch into the TraceMonkey branch. And yesterday, the now combined JM+TM have been merged into mozilla-central, which is the "trunk".


Sorry about getting the terminology mixed. As I understood it, the now combined JM+TM is JaegerMonkey. Before now there has been no JM+TM, there has only been tracing JIT or method JIT, and no engine which combined them.

The tracing JIT and method JIT components have indeed each been in separate development for quite some time. It is the combination, the merged JM+TM (AFAIK this is called Jaegermonkey) which is only about two weeks old.

Reply Parent Score: 2

smitty Member since:
2005-10-13

Sorry about getting the terminology mixed. As I understood it, the now combined JM+TM is JaegerMonkey. Before now there has been no JM+TM, there has only been tracing JIT or method JIT, and no engine which combined them.

The tracing JIT and method JIT components have indeed each been in separate development for quite some time. It is the combination, the merged JM+TM (AFAIK this is called Jaegermonkey) which is only about two weeks old.


No that's wrong and the other poster is correct.

Jaegermonkey = method JIT compiler
Tracemonkey = tracing JIT compiler
Spidermonkey = generic name for the full javascript compiler, which now contains bother Jaeger and Trace monkeys.

Reply Parent Score: 2

Gusar Member since:
2010-07-16

No, the merged part is not JaegerMonkey. Only JaegerMonkey is JaegerMonkey (duh ;) ).
The whole thing combined is, as it always was, SpiderMonkey.

Reply Parent Score: 1