Talk:List of ECMAScript engines

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing (Rated List-class, Low-importance)
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 List  This article has been rated as List-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.

What scripting engines are used by Openwave, Opera mini, or the Nokia or Motorola browsrs? Mathiastck 12:14, 19 July 2007 (UTC)

Redlinks to be avoided.[edit]

Are all the red links in this articles that need to be created and have notability? --Pmedema (talk) 05:36, 18 August 2008 (UTC)

It looks like many of them are libraries built around the SpiderMonkey engine, rather than ECMAScript engines in their own right. (talk) 05:10, 25 August 2008 (UTC)

Source missing[edit]

"SpiderMonkey — JavaScript engine in Mozilla Gecko applications, including Firefox. Adobe also uses it in Flash Media Server." . References on where this usage by Adobe FMS is declared ? —Preceding unsigned comment added by (talk) 06:48, 2 September 2010 (UTC)


Should this not be swaped with trace monkey? Wyatt Childers (talk) 20:33, 17 September 2010 (UTC)


This page makes no mention of BESEN, a new Object Pascal ECMAScript engine. Apparently the first engine that was entirely ECMAScript 5 compliant - —Preceding unsigned comment added by (talk) 19:19, 2 May 2011 (UTC)


Rhino is listed as "interpreted only". However, it can and does compile the JS into Java bytecode, which in turn can be JIT compiled by the JVM into machine code.

I don't believe Rhino has a JIT. You can explicitly tell it to compile a given script as a whole, or to interpret it. All this information is available in the Rhino page.

So while it doesn't fit into the JIT group, it's not accurate to leave it in the "interpreted only" group either.

Out of curiosity, I started looking into the other JS engines listed as "interpreted only".

  • QtScript: now uses JavaScriptCore (Nitro)
  • LinearB: redirects to Opera's Presto_(layout_engine)#JavaScript_engines. Opera currently uses Carakan. I suggest listing the other JS engines Opera has used as well, or pulling LinearB from the list.
  • JKS: An evolutionary predecessor to JavaScriptCore which in turn became SquirrelFish/Nitro.
  • Furthark: in the same boat as LinearB, a JS engine used by older versions of Opera.

--Mstorer (talk) 17:39, 5 October 2011 (UTC)

SquirrelFish & JavaScriptCore[edit]

Should really SquirrelFish be shown separately from JavaScriptCore? SquirrelFish is an incremental rewrite of JavaScriptCore which has finally been integrated to Webkit [1] Despite this rewrite, it is still called JavaScriptCore. [2] Alexandre.Morgaut (talk) 12:00, 6 June 2012 (UTC)

Javascript in PDF[edit]

The page misses to mention that PDF supports embedded JavaScript, and so Adobe Acrobat reader supports JavaScript and it has A LOT of installations. Here are key references for this sub-topic:

  • API reference from Adobe [3]
  • PDF: Adobe's JavaScript™ for Acrobat® API Reference, 2007 [4]
  • Stackoverflow with links to books, video and slides with in-depth material [5]

I suggest adding this into the runtime-interpreters section after Rhino, because it's not well-known but certainly well-installed. Perhaps with wording like this below:

JavaScript for Acrobat: Adobe's engine running scripts embedded inside PDF (implementation details of the engine are unconfirmed)

Also note this engine is mentioned in other Wikipedia pages already: