<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Adobe Open Sources JavaScript Engine in Mozilla Foundation</title>
	<atom:link href="http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Sat, 20 Mar 2010 13:30:04 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Yoko</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-254123</link>
		<dc:creator>Yoko</dc:creator>
		<pubDate>Mon, 20 Aug 2007 01:13:10 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-254123</guid>
		<description>Agreed.</description>
		<content:encoded><![CDATA[<p>Agreed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-253320</link>
		<dc:creator>david</dc:creator>
		<pubDate>Mon, 30 Jul 2007 14:46:30 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-253320</guid>
		<description>Wow!!! that is big news. thanks man :)
________________
&lt;b&gt;&lt;a href=&quot;http://www.dl4all.com&quot; rel=&quot;nofollow&quot;&gt;Free Software&lt;/a&gt; &#124; &lt;a href=&quot;http://www.4shared.us&quot; rel=&quot;nofollow&quot;&gt;Top Share Site&lt;/a&gt; &#124; &lt;a href=&quot;http://www.parsiforums.com&quot; rel=&quot;nofollow&quot;&gt;Ù…ÙˆØ¨Ø§ÛŒÙ„ ØŒ Ú©Ø§Ù…Ù¾ÛŒÙˆØªØ±&lt;/a&gt;&lt;/b&gt;</description>
		<content:encoded><![CDATA[<p>Wow!!! that is big news. thanks man :)<br />
________________<br />
<b><a href="http://www.dl4all.com" rel="nofollow">Free Software</a> | <a href="http://www.4shared.us" rel="nofollow">Top Share Site</a> | <a href="http://www.parsiforums.com" rel="nofollow">Ù…ÙˆØ¨Ø§ÛŒÙ„ ØŒ Ú©Ø§Ù…Ù¾ÛŒÙˆØªØ±</a></b></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Backdrifter: Adobe Donates ActionScript VM to Mozilla</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-171911</link>
		<dc:creator>Backdrifter: Adobe Donates ActionScript VM to Mozilla</dc:creator>
		<pubDate>Thu, 09 Nov 2006 07:41:38 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-171911</guid>
		<description>[...] Adobe Open Sources JavaScript Engine in Mozilla Foundation at Ajaxian [...]</description>
		<content:encoded><![CDATA[<p>[...] Adobe Open Sources JavaScript Engine in Mozilla Foundation at Ajaxian [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Elliott</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-170865</link>
		<dc:creator>Steven Elliott</dc:creator>
		<pubDate>Wed, 08 Nov 2006 16:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-170865</guid>
		<description>Apologies for jumping the gun.  I just took a look at Tamarin CVS and found disappointingly there is no support for AS3 only ES4.  Oh well, it seemed possible if not probable.</description>
		<content:encoded><![CDATA[<p>Apologies for jumping the gun.  I just took a look at Tamarin CVS and found disappointingly there is no support for AS3 only ES4.  Oh well, it seemed possible if not probable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Elliott</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-170798</link>
		<dc:creator>Steven Elliott</dc:creator>
		<pubDate>Wed, 08 Nov 2006 15:53:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-170798</guid>
		<description>As I understand the press releases AVM2 will compile and run AS3 in Mozilla.  If this is the case a couple of things become possible (and probably more).  You will have access to the AS3 API which includes XMLSocket, NetConnection, NetConnectionChannel, et al.  This could not only replace XHR but would provide a ready made solution for reverse Ajax / Comet (directly replacing ad hoc solutions like AjaF).  Going one step further you have SharedObject API for collaborative API.  I realize a lot of this depends on server-side code but I guess my question is &quot;How much of the AS3 API is Tamarin going to run on the clientside?&quot;.  Anybody?</description>
		<content:encoded><![CDATA[<p>As I understand the press releases AVM2 will compile and run AS3 in Mozilla.  If this is the case a couple of things become possible (and probably more).  You will have access to the AS3 API which includes XMLSocket, NetConnection, NetConnectionChannel, et al.  This could not only replace XHR but would provide a ready made solution for reverse Ajax / Comet (directly replacing ad hoc solutions like AjaF).  Going one step further you have SharedObject API for collaborative API.  I realize a lot of this depends on server-side code but I guess my question is &#8220;How much of the AS3 API is Tamarin going to run on the clientside?&#8221;.  Anybody?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rob cherny</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-170549</link>
		<dc:creator>rob cherny</dc:creator>
		<pubDate>Wed, 08 Nov 2006 13:24:34 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-170549</guid>
		<description>On my site where &lt;a href=&quot;http://www.cherny.com/webdev/49/adobe-open-sources-actionscript-engine-with-the-mozilla-foundation&quot; rel=&quot;nofollow&quot;&gt;I posted about this&lt;/a&gt;, I was concentrating on the &quot;killing two birds with one stone&quot; aspect, but I wasn&#039;t even aware of the performance gains to be had. Very cool indeed. Can&#039;t wait.</description>
		<content:encoded><![CDATA[<p>On my site where <a href="http://www.cherny.com/webdev/49/adobe-open-sources-actionscript-engine-with-the-mozilla-foundation" rel="nofollow">I posted about this</a>, I was concentrating on the &#8220;killing two birds with one stone&#8221; aspect, but I wasn&#8217;t even aware of the performance gains to be had. Very cool indeed. Can&#8217;t wait.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Eich</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-169265</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Wed, 08 Nov 2006 00:39:21 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-169265</guid>
		<description>Jim Ray: you&#039;ve got it. Lately, when I speak, I hear requests for a standard bytecode format for JS. My answer is that the bytecoded, JITed VM space is a patent-encrusted mess, which means sunk costs of significant size. So I doubt there will be a standard JS bytecode, but I do suspect that a standard binary syntax for Abstract Syntax Trees (ASTs) could be agreed upon, based on the interfaces for reflecting on ASTs that we are working on for ES4. And binary-ASTs can be *more* efficient, both for transfer and for JITing, than binary bytecode formats.

/be</description>
		<content:encoded><![CDATA[<p>Jim Ray: you&#8217;ve got it. Lately, when I speak, I hear requests for a standard bytecode format for JS. My answer is that the bytecoded, JITed VM space is a patent-encrusted mess, which means sunk costs of significant size. So I doubt there will be a standard JS bytecode, but I do suspect that a standard binary syntax for Abstract Syntax Trees (ASTs) could be agreed upon, based on the interfaces for reflecting on ASTs that we are working on for ES4. And binary-ASTs can be *more* efficient, both for transfer and for JITing, than binary bytecode formats.</p>
<p>/be</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Ray</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168808</link>
		<dc:creator>Jim Ray</dc:creator>
		<pubDate>Tue, 07 Nov 2006 21:07:20 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168808</guid>
		<description>Hey, thanks, Brendan!

I guess what I meant when I said that &quot;JS is never compiled&quot; is that it&#039;s never compiled by the developer, e.g. it&#039;s still interpreted by the browser first, not dropped on the webserver as a compiled object (like a Java applet or a Flash SWF). So, the way I understand this is that there will be a generic JS -&gt; bytecode compiler and then a platform specific bytecode -&gt; machine code JIT that will further improve performance.</description>
		<content:encoded><![CDATA[<p>Hey, thanks, Brendan!</p>
<p>I guess what I meant when I said that &#8220;JS is never compiled&#8221; is that it&#8217;s never compiled by the developer, e.g. it&#8217;s still interpreted by the browser first, not dropped on the webserver as a compiled object (like a Java applet or a Flash SWF). So, the way I understand this is that there will be a generic JS -&gt; bytecode compiler and then a platform specific bytecode -&gt; machine code JIT that will further improve performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Sanheim</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168720</link>
		<dc:creator>Rob Sanheim</dc:creator>
		<pubDate>Tue, 07 Nov 2006 20:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168720</guid>
		<description>Nice blog post summarizing what this means for everyone involved:

http://www.hecker.org/mozilla/adobe-mozilla-and-tamarin</description>
		<content:encoded><![CDATA[<p>Nice blog post summarizing what this means for everyone involved:</p>
<p><a href="http://www.hecker.org/mozilla/adobe-mozilla-and-tamarin" rel="nofollow">http://www.hecker.org/mozilla/adobe-mozilla-and-tamarin</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168703</link>
		<dc:creator>Jeffrey</dc:creator>
		<pubDate>Tue, 07 Nov 2006 20:25:34 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168703</guid>
		<description>To Andreas Ecker: Just saw that myself on Ars and double checked here - thanks!</description>
		<content:encoded><![CDATA[<p>To Andreas Ecker: Just saw that myself on Ars and double checked here &#8211; thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Eich</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168675</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Tue, 07 Nov 2006 19:54:53 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168675</guid>
		<description>Jim Ray: JS is compiled in Firefox to bytecode, so it&#039;s not true that &quot;JS is never compiled.&quot;  Some browsers parse to abstract syntax trees (ASTs) and interpret those recursively; others compile to continuations, as if the JS were Scheme or a Lisp dialect.  In any event, JS can be JITed to gain performance.  Untyped JS as is found on the web will need special care to realize the same gains that typed AS3 code sees in Flash 9.

/be</description>
		<content:encoded><![CDATA[<p>Jim Ray: JS is compiled in Firefox to bytecode, so it&#8217;s not true that &#8220;JS is never compiled.&#8221;  Some browsers parse to abstract syntax trees (ASTs) and interpret those recursively; others compile to continuations, as if the JS were Scheme or a Lisp dialect.  In any event, JS can be JITed to gain performance.  Untyped JS as is found on the web will need special care to realize the same gains that typed AS3 code sees in Flash 9.</p>
<p>/be</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JD on EP</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168594</link>
		<dc:creator>JD on EP</dc:creator>
		<pubDate>Tue, 07 Nov 2006 18:41:09 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168594</guid>
		<description>&lt;strong&gt;Tamarin commentary, day 1&lt;/strong&gt;

Tamarin commentary, day 1: Through the day I&#039;ll be updating this entry with links &amp; pullquotes I find particularly interesting. It&#039;s like drinking from a firehose, though... Adobe&#039;s donation to Mozilla of scripting engine sourcecode will take us all...</description>
		<content:encoded><![CDATA[<p><strong>Tamarin commentary, day 1</strong></p>
<p>Tamarin commentary, day 1: Through the day I&#8217;ll be updating this entry with links &amp; pullquotes I find particularly interesting. It&#8217;s like drinking from a firehose, though&#8230; Adobe&#8217;s donation to Mozilla of scripting engine sourcecode will take us all&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Ecker</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168566</link>
		<dc:creator>Andreas Ecker</dc:creator>
		<pubDate>Tue, 07 Nov 2006 18:05:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168566</guid>
		<description>Fortunately, Jeffrey, we won&#039;t have to wait til 2010 :-). From the &lt;a href=&quot;http://www.mozilla.org/projects/tamarin/&quot; rel=&quot;nofollow&quot;&gt;Tamarin project page&lt;/a&gt; at Mozilla: &quot;Tamarin will support the forthcoming ECMAScript Edition 4 (&#039;&#039;JS&#039;&#039;) language and will be integrated into SpiderMonkey as part of the Mozilla 2 project, to be released in 2008&quot;.
 
Recently Brendan Eich made various rather &lt;a href=&quot;http://blog.qooxdoo.org/project-tamarin-to-boost-javascript&quot; rel=&quot;nofollow&quot;&gt;mysterious statements&lt;/a&gt; about a forthcoming open source JavaScript VM. Definitely, this is going to change the future of browser-based applications!
 For  the Open Source JavaScript framework &lt;a href=&quot;http://qooxdoo.org&quot; rel=&quot;nofollow&quot;&gt;qooxdoo&lt;/a&gt; (as well as all the other JavaScript frameworks), this is particularly great news as it had recently already revealed the &lt;a href=&quot;http://ajaxian.com/archives/dramatically-improved-ie7-javascript-performance&quot; rel=&quot;nofollow&quot;&gt;major performance improvements of IE7&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Fortunately, Jeffrey, we won&#8217;t have to wait til 2010 :-). From the <a href="http://www.mozilla.org/projects/tamarin/" rel="nofollow">Tamarin project page</a> at Mozilla: &#8220;Tamarin will support the forthcoming ECMAScript Edition 4 (&#8221;JS&#8221;) language and will be integrated into SpiderMonkey as part of the Mozilla 2 project, to be released in 2008&#8243;.</p>
<p>Recently Brendan Eich made various rather <a href="http://blog.qooxdoo.org/project-tamarin-to-boost-javascript" rel="nofollow">mysterious statements</a> about a forthcoming open source JavaScript VM. Definitely, this is going to change the future of browser-based applications!<br />
 For  the Open Source JavaScript framework <a href="http://qooxdoo.org" rel="nofollow">qooxdoo</a> (as well as all the other JavaScript frameworks), this is particularly great news as it had recently already revealed the <a href="http://ajaxian.com/archives/dramatically-improved-ie7-javascript-performance" rel="nofollow">major performance improvements of IE7</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Ray</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168544</link>
		<dc:creator>Jim Ray</dc:creator>
		<pubDate>Tue, 07 Nov 2006 17:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168544</guid>
		<description>So, can someone explain to me what the advantage of having a JIT is for web developers, specifically as it relates to Javascript? My understanding of JIT is that it takes bytecode, like what you get from a Java app or SWF, and translates it to machine code, tuned to specific platforms, at runtime.

But since JS is never compiled, I don&#039;t understand the advantage of dynamic translation for JS. Am I missing something?</description>
		<content:encoded><![CDATA[<p>So, can someone explain to me what the advantage of having a JIT is for web developers, specifically as it relates to Javascript? My understanding of JIT is that it takes bytecode, like what you get from a Java app or SWF, and translates it to machine code, tuned to specific platforms, at runtime.</p>
<p>But since JS is never compiled, I don&#8217;t understand the advantage of dynamic translation for JS. Am I missing something?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: è‹¦ç‰¢ä¹‹æœ€å¾Œä¸€å¹´</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168500</link>
		<dc:creator>è‹¦ç‰¢ä¹‹æœ€å¾Œä¸€å¹´</dc:creator>
		<pubDate>Tue, 07 Nov 2006 17:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168500</guid>
		<description>&lt;strong&gt;Tamarin = Flash + JavaScript + ?&lt;/strong&gt;

æƒ³åˆ°ä»¥å¾Œå¯èƒ½å¯ä»¥ä¸ç”¨è£ flash player æˆ‘å°±è¦ºå¾—è »é«˜èˆˆçš„&#8230; :p

å‰›å‰›çœ‹åˆ°ä¸€å‰‡æ¶ˆæ¯ï¼Œèªªæ˜¯ Adobe æŠŠå®ƒå€‘çš„ ActionScript virtual machine çš„ç¨‹å¼çµ¦ open source äº†ï¼Œäº¤ä»˜çµ¦ Mozilla ä½¿ç”¨ï¼Œæ”¹åå«åš Tamarin (ä¸æ˜¯ ...</description>
		<content:encoded><![CDATA[<p><strong>Tamarin = Flash + JavaScript + ?</strong></p>
<p>æƒ³åˆ°ä»¥å¾Œå¯èƒ½å¯ä»¥ä¸ç”¨è£ flash player æˆ‘å°±è¦ºå¾—è »é«˜èˆˆçš„&#8230; :p</p>
<p>å‰›å‰›çœ‹åˆ°ä¸€å‰‡æ¶ˆæ¯ï¼Œèªªæ˜¯ Adobe æŠŠå®ƒå€‘çš„ ActionScript virtual machine çš„ç¨‹å¼çµ¦ open source äº†ï¼Œäº¤ä»˜çµ¦ Mozilla ä½¿ç”¨ï¼Œæ”¹åå«åš Tamarin (ä¸æ˜¯ &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dion Almaer</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168429</link>
		<dc:creator>Dion Almaer</dc:creator>
		<pubDate>Tue, 07 Nov 2006 16:22:05 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168429</guid>
		<description>JZ,

Flash uses ActionScript which is ECMAScript (the standard). JavaScript, JScript, are implementations of the ECMAScript standard.

Basically, Flash runs on what you think of as a JavaScript VM :)

Cheers,

Dion</description>
		<content:encoded><![CDATA[<p>JZ,</p>
<p>Flash uses ActionScript which is ECMAScript (the standard). JavaScript, JScript, are implementations of the ECMAScript standard.</p>
<p>Basically, Flash runs on what you think of as a JavaScript VM :)</p>
<p>Cheers,</p>
<p>Dion</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JZ</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168424</link>
		<dc:creator>JZ</dc:creator>
		<pubDate>Tue, 07 Nov 2006 16:09:53 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168424</guid>
		<description>Umm. I see Flash and javascript mentioned here. I didn&#039;t realize that Flash used javascript. Obviously I&#039;m confused. Can someone please explain the significance of the announcement in simple terms? Also, does this give give significant strategic advantage to Mozilla over MS/IE?</description>
		<content:encoded><![CDATA[<p>Umm. I see Flash and javascript mentioned here. I didn&#8217;t realize that Flash used javascript. Obviously I&#8217;m confused. Can someone please explain the significance of the announcement in simple terms? Also, does this give give significant strategic advantage to Mozilla over MS/IE?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iface thoughts &#187; Tamarin - A Contribution From Adobe</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168328</link>
		<dc:creator>iface thoughts &#187; Tamarin - A Contribution From Adobe</dc:creator>
		<pubDate>Tue, 07 Nov 2006 15:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168328</guid>
		<description>[...] Ajaxian breaks this news about Adobe contributing source code from the FlashPlayer Scripting Engine to the Mozilla Foundation. This will take the form of a new project called Tamarin. It will continue to be used by Adobe as part of the ActionScript(tm) Virtual Machine within Adobe Flash Player. Not only does this open it to the community, but will ensure tighter integration with the open source and cross-platform browser Firefox. This is also a good news for Linux community as this might lead to a better experience with Flash in future. Kudos to Adobe! [...]</description>
		<content:encoded><![CDATA[<p>[...] Ajaxian breaks this news about Adobe contributing source code from the FlashPlayer Scripting Engine to the Mozilla Foundation. This will take the form of a new project called Tamarin. It will continue to be used by Adobe as part of the ActionScript(tm) Virtual Machine within Adobe Flash Player. Not only does this open it to the community, but will ensure tighter integration with the open source and cross-platform browser Firefox. This is also a good news for Linux community as this might lead to a better experience with Flash in future. Kudos to Adobe! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey</title>
		<link>http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla/comment-page-1#comment-168285</link>
		<dc:creator>Jeffrey</dc:creator>
		<pubDate>Tue, 07 Nov 2006 14:51:37 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/adobe-open-sources-javascript-engine-in-mozilla#comment-168285</guid>
		<description>Wow - that is big news.  Previous discussion made it appear that a JIT Javascript compiler would be 2010 thing for Firefox.  Now I would like to speculate that it will be much sooner(?)</description>
		<content:encoded><![CDATA[<p>Wow &#8211; that is big news.  Previous discussion made it appear that a JIT Javascript compiler would be 2010 thing for Firefox.  Now I would like to speculate that it will be much sooner(?)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
