From MozillaWiki
Jump to: navigation, search
Ambox outdated.png THIS PAGE IS OBSOLETE
This article is in parts, or in its entirety, outdated. Hence, the information presented on this page may be incorrect, and should be treated with due caution. Visit for more up to date information.

This is a non-exhaustive list of people who regularly hack on SpiderMonkey: Rooting, Baseline, Frontend, and all projects (named and unnamed) and technical areas beneath it.

If you regularly work on the JavaScript engine, feel free to add yourself to the lists below, and to make corrections and updates to it as needed.

Finding a Peer

Project Short Description IRC Peers
IonMonkey Optimizing Just-In-Time Compiler sstangl, mjrosenb, h4writer, nbp, djvj, jandem
Baseline Compiler Fast Just-In-Time Compiler jandem, djvj
OdinMonkey asm.js parser & MIR generation luke, sstangl
Frontend Parser & Bytecode generation jorendorff, ejpbruel, luke, arai
Interpreter Interpreter! jorendorff, luke
GC Rooting & Marking & Sweeping terrence, jonco, sfink, ehoogeveen, pbone
Parallel JS Prototype implementation of parallel array methods shu, nmatsakis, pnkfelix
Self-hosting Builtins implemented in JavaScript till, Waldo, shu, nmatsakis, arai
Intl Internationalization support, Ecma 402 norbert, Waldo
EcmaScript Script reading Waldo, jorendorff, till
Debugging Debugger API, etc jimb, jorendorff, ejpbruel
Test suites Setup, inner workings terrence
JSObject and children Internal object representation jorendorff, Waldo, luke
Strings Internal string representation evilpie, luke
Proxies, Wrappers ES (in)direct proxies, COWs jorendorff, ejpbruel, evilpie, till
Yarr Our import of JSC's RegExp JIT sstangl
irregexp Our import of V8's RegExp JIT arai
ctypes Well, ctypes yoric

Regular JavaScript engine hackers

These people regularly hack on the JavaScript engine. If you're looking for someone who knows a particular concept well, to ask questions about it, clarify concepts, &c., this is a good place to look. (And if you hack regularly on the JavaScript engine, feel free to add yourself and mention whatever areas you're comfortable in.)

(NB: Email addresses aren't listed for spam-prevention purposes. To find out an email address, type the listed Bugzilla identifier in the CC box on bmo and look at the autocompletion.)

(Please keep this list in alphabetical order by last name.)

Name Bugzilla ID Areas of expertise
Jim Blandy :jimb Debugger support, front end, strict mode, build system
Paul Bone :pbone GC
Jacob Bramley :jbramley ARM
Igor Bukanov igor@mir2 GC
Terrence Cole :terrence GC
Jan de Mooij jandem
Brendan Eich :brendan JSAPI, shapes
Steve Fink :sfink GC, static hazard analysis, shell, structured clone, typed arrays, continuous integration
Tooru Fujisawa :arai frontend, self-hosting, async/await, regexp
Andreas Gal :gal Proxies, wrappers, GC
Dave Herman dherman@moz Reflection API
Blake Kaplan :mrbkap Proxies and wrappers, the interpreter, using the JSAPI
Bill McCloskey billm@moz GC
Nicholas Nethercote :njn Memory allocation and measurement, scanner, front-end
Jason Orendorff jorendorff@moz being on IRC (just ask)
Till Schneidereit :till Self-hosting, ECMAScript spec, some familiarity with parsing, proxies, various things in the engine.
Tom Schuster evilpie IonMonkey, Baseline, some Rooting, Unicode support, ECMAScript spec, strings, proxies and in particular CPOWs
Sean Stangl sstangl@moz JS JITs: JaegerMonkey, IonMonkey.
Kannan Vijayan :djvj BaselineCompiler, ICs, IonMonkey
Gregor Wagner anygregor@gm GC
Luke Wagner :luke Stack, values, containers, generators, C++ language lawyer
Jeff Walden jwalden+bmo JSON, ES5 spec, strict mode, arguments objects, typed arrays, some familiarity with JavaScript stack/frame layout/etc. (but prefer Luke)

Hackers emeriti

These people once regularly hacked on the JavaScript engine but don't do so regularly any more. Reviewers listed here may or may not be willing to review patches. If they aren't, they'll say so when review is requested of them and perhaps forward it to a better person.

(Please keep this list in alphabetical order by last name.)

Name Bugzilla ID Areas of expertise
Paul Biggar paul.biggar JSON (prefer Waldo), build system, testing, memory allocation
Brian Crowder crowderbt@
Graydon Hoare graydon@moz
Christopher D. Leary :cdleary Inline caches, regular expressions, yarr, parser, scanner, ARM, GDB
David Anderson :dvander IonMonkey
David Mandelin dmandelin@moz Method JIT, name lookup
Mike Shaver :shaver