Parts of this article (those related to how and when it was discontinued) need to be updated. Please help update this article to reflect recent events or newly available information.(August 2022)
The source code, including the just-in-time compiler and conservative garbage collector, was donated to the Mozilla Foundation on November 7, 2006.[3] The contributed code is tri-licensed under the GPL, LGPL, and MPL licenses to be developed in Mozilla's Mercurial repository.[4] The contributed code is approximately 135,000 lines of code,[5] making it the largest single donation of code to the Mozilla project besides Netscape itself.[6]
There were plans to use Tamarin as part of Mozilla 2[7] (and therefore Firefox 4). The project to integrate Tamarin and SpiderMonkey was called "ActionMonkey",[8] but was canceled in 2008[9] because Tamarin's interpreter turned out to be slower than SpiderMonkey's and because the plans of ECMAScript development shifted from ECMAScript 4, which was partially implemented by then existing Tamarin source code and was meant to be completed by joined efforts of Adobe, Mozilla and its community within the Tamarin Project,[10] to ECMAScript Harmony.[11]
Adobe continued to use Tamarin in its Flash Player, but it did not replace SpiderMonkey as the JavaScript engine of Mozilla applications.
The only part of Tamarin used in modern Mozilla applications (i.e. Firefox 3.5+) via SpiderMonkey is NanoJIT, a module that is used to generate native code when performing just-in-time compilation.[12]
What Tamarin is not
Adobe contributed code for its ActionScript Virtual Machine 2 and the JIT compiler. The ActionScript compiler is also open source as a part of Adobe Flex.[13] There is also CrossBridge, an open source C and C++ compiler.
Tamarin is not the same as Adobe Flash Player, which remains closed source. The Tamarin virtual machine is only a part of Flash Player.
Related projects
Two projects related to Tamarin were announced on July 25, 2007, in Brendan Eich's keynote at The Ajax Experience West: IronMonkey and ScreamingMonkey.[14][15] IronMonkey is a project to map IronPython and IronRuby to Tamarin led by Seo Sanghyeon.[16] ScreamingMonkey's goal is to allow Tamarin to run within non-Mozilla browsers (thus allowing them to understand JavaScript 2), starting with Internet Explorer. The project is led by Mark Hammond.[17] Neither project had production-quality releases and their current status is unclear.
Etymology
Both SpiderMonkey and Tamarin fulfill closely related goals and so were given names derived from types of monkeys (the spider monkey and the tamarin, respectively).
^Melanson, Mike (November 7, 2006). "Open Up". Penguin.SWF — Just another Adobe Blog site. Archived from the original on July 4, 2008. Retrieved September 3, 2010.
^Eich, Brendan (October 13, 2006). "Mozilla 2". Brendan's Roadmap Updates. MozillaZine. Archived from the original on October 25, 2006. Retrieved September 3, 2010.
^Resig, John (July 23, 2007). "ActionMonkey". John Resig Blog. Retrieved September 3, 2010.
^Eich, Brendan (July 25, 2007). "New Projects". Brendan's Roadmap Updates. MozillaZine. Archived from the original on November 14, 2010. Retrieved September 3, 2010.
