Implications of the Mozilla/Adobe Partnership 104
Fraggle writes "Recently the Mozilla Foundation and Adobe announced a partnership, working together on the next generation
JavaScript/ActionScript JIT Virtual Machine. The Browser Den looks at what this means for the future of scripting in Mozilla, and how this partnership with Adobe may affect Mozilla's support for other technologies such as SVG." From the article: "On the Mozilla side the plan is to integrate to code with SpiderMonkey which is Mozilla's current JavaScript implementation that is written in C. This is needed because Tamarin is not a drop-in replacement for SpiderMonkey as it provides necessary features that are not available in Tamarin. The combined SpiderMonkey with integrated Tamarin should not have any problems with old JavaScript and should show a performance boost for most. However, skilled scripters are sure to find ways of optimising performance to get even more gains."
Amazing (Score:2, Insightful)
HTML either, but that preconception was crushed when I saw the money those art school dropouts were making.
I just hope that they don't embed Flash player into the browser. That would suck royally.
Say What? (Score:5, Insightful)
I presume the article means to say that the Tamarin engine will be coupled with SpiderMonkey's APIs? Because I don't see how you could "combine" two separate Javascript engines and expect a usable result. That would be like "combining" Windows and Mac OS X to make a better operating system. It doesn't quite work that way.
Re:Is Open Source finally ready for prime time? (Score:2, Insightful)