Hacker News Reader

Comment by evilpie | Hacker News Reader

https://bugzilla.mozilla.org/show_bug.cgi?id=840282 has some measurements on how fast the implementation of asm.js (called OdinMonkey) already is. "sm" is SpiderMonkey, that is the normal JS engine. v8 is Chrome's JavaScript engine.

Current results on large Emscripten codebases are as follows, reported as factor slowdown compared to gcc -O2 (so 1.0 would mean "same speed")

               odin (now)  odin (next)  sm      v8  
  skinning     2.80        2.46         12.90   59.35  
  zlib         2.02        1.61         5.15    5.95  
  bullet       2.16        1.79         12.31   9.30

View on HN

I kinda hope that someone at Mozilla keeps a count of just how many monkeys have gone into the code base. Off the top of my head, there's SpiderMonkey, TraceMonkey, JagerMonkey, IonMonkey, ScreamingMonkey, IronMonkey, and perhaps you should count Tamarin. It would be neat to see mascot like versions of them all... :)

We have/had t-shirts and posters for JägerMonkey and IonMonkey. https://secure.flickr.com/photos/vikingkarwur/8312701001/

I've never heard of ScreamingMonkey or IronMonkey, and I'm a member of Mozilla's JavaScript team...

IronMonkey was apparently for "mapping IronPython and IronRuby (and maybe IronPHP) to Tamarin". I just vaguely recalled seeing the name pop up in a Mozilla related context -- I certainly couldn't have told you what it was without looking it up. :)

https://wiki.mozilla.org/Tamarin:IronMonkey

I've never heard of IronMonkey but ScreamingMonkey was at least planned as a Tamarin replaces js engine in IE project:

https://wiki.mozilla.org/Tamarin:ScreamingMonkey

Reply on news.ycombinator.com