Comments on: tamarin, ecmascript4, as3, webkit and air

By: Joshua Mostafa

Joshua Mostafa — Tue, 22 Jul 2008 23:15:56 +0000

Yes, very crooked :) You’re comparing grapes with grapefruit.

Tamarin cannot replace Webkit; they do different jobs. Webkit is an HTML rendering engine. Tamarin is an ES4 (or as we know it, AS3) interpreter.

My original post is speculative – talking about what may happen in the future. If you just need some basic information regarding AIR, maybe try Adobe’s website.

By: coder

coder — Tue, 22 Jul 2008 18:50:21 +0000

Investigating AIR, it was confusing to see webkit,AVM2, tamarin etc. My inference from Mike’s comments is that Webkit does not want to adopt AVM2 into its one stop solution …

So the reading I get is that webkit will be replaced by tamarin in AIR… crooked thinking?

By: Joshua Mostafa

Joshua Mostafa — Tue, 22 Apr 2008 06:52:08 +0000

Good point Mike.

Do you see a future with ECMAScript4 for HTML in AIR, then – or do you at least agree it would be a good thing?

By: mike chambers

mike chambers — Tue, 22 Apr 2008 02:28:08 +0000

> Adobe on the one hand working with the Mozilla folks to coordinate ECMAScript in both Tamarin and Flash/AIR, and then using WebKit as part of its AIR platform?

Keep in mind that we didnt just donate Tamarin to Mozilla, we donated it to everyone. i.e. it is an open license that anyone can use… (including webkit)…

mike chambers

mesh@adobe.com

By: JesterXL

JesterXL — Tue, 22 Apr 2008 01:44:04 +0000

I know jack about the technical details, but I think embedding Gecko is REALLY frikin’ hard… or just doesn’t work. Details here:

http://nick.typepad.com/blog/2008/03/can-mozilla-be.html

Nokia had the same issues building their own browser for phones, gave up, and officially sanctioned on WebKit. If it just works, why not? Hey, that phrase sounds familiar…