tag:tenfourfox.tenderapp.com,2012-01-07:/discussions/suggestions/12-landmark-compromiseTenFourFox: Discussion 2012-03-02T01:21:27Ztag:tenfourfox.tenderapp.com,2012-01-07:Comment/136201682012-02-11T20:54:02Z2012-02-11T20:54:02ZLandmark Compromise<div><p>Interesting, but highly unlikely. Camino is going to drop Gecko
as fas as I know, so it won't benefit from further PPC jit
development. And even though Camino is a fine browser with its own
philosophy, TFF is even more unlikely to adopt the Camino frontend
(lacking add-ons and other features). Sorry.</p></div>Chris (chtrusch)tag:tenfourfox.tenderapp.com,2012-01-07:Comment/136201682012-02-11T21:29:39Z2012-02-11T21:29:39ZLandmark Compromise<div><p>Chris is right. Camino can't utilize Mozilla 2.x and higher
because they don't support embedding, which is why Camino is moving
away from Gecko in the first place. Secondly, the JIT in Camino is
an older version of the tracejit, which Mozilla doesn't support
anymore, and our old tracejit will need modification for LIRops the
3.6 JS engine can generate that were removed in the update to
Firefox 4. You can certainly take a whack at this yourself, but it
will never be as fast as JM+TI will be because it doesn't support
the optimizations available in later versions of JavaScript. It's
not something I plan to work on, however.</p></div>Cameron Kaiser