The document compares the performance of JavaScript engines in different browsers. It discusses the V8 engine in Google Chrome, SpiderMonkey in Firefox, Chakra in Internet Explorer 9, and Carakan in Opera 11. Benchmarks show that V8 consistently outperforms the other engines, with Chrome 16 being 2-5 times faster than Firefox, Internet Explorer, and Opera in the Kraken and V8 benchmarks. The document attributes V8's performance to optimizations like hidden classes, dynamic code generation, and its garbage collector.
The document compares the performance of JavaScript engines in different browsers. It discusses the V8 engine in Google Chrome, SpiderMonkey in Firefox, Chakra in Internet Explorer 9, and Carakan in Opera 11. Benchmarks show that V8 consistently outperforms the other engines, with Chrome 16 being 2-5 times faster than Firefox, Internet Explorer, and Opera in the Kraken and V8 benchmarks. The document attributes V8's performance to optimizations like hidden classes, dynamic code generation, and its garbage collector.
Active Scripting was the interface used by Internet Explorer versions 3 through 8 to bind scripting engines like JScript and VBScript. It provided COM interfaces for the scripting engine and host applications to communicate. Active Scripting was used by IE, Windows Script Host, ASP, Office applications, and other third party apps to integrate scripting. It required scripting engines to implement interfaces like IAcriptScript and allowed hosts like IE to debug scripts through COM debugging APIs. With IE9, Microsoft moved to a new scripting model that replaced Active Scripting.
This document discusses Firefox OS and its use of e10s (electrolysis) architecture. It covers the process model used in Firefox OS including the b2g process, plugin container process, and hardware access. It also summarizes the Inter-Process Communication (IPC) mechanisms like IPDL, network APIs like XMLHttpRequest and WebSockets, as well as inter-app communication capabilities in Firefox OS like Web Activities and direct app connections.
Active Scripting was the interface used by Internet Explorer versions 3 through 8 to bind scripting engines like JScript and VBScript. It provided COM interfaces for the scripting engine and host applications to communicate. Active Scripting was used by IE, Windows Script Host, ASP, Office applications, and other third party apps to integrate scripting. It required scripting engines to implement interfaces like IAcriptScript and allowed hosts like IE to debug scripts through COM debugging APIs. With IE9, Microsoft moved to a new scripting model that replaced Active Scripting.
This document discusses Firefox OS and its use of e10s (electrolysis) architecture. It covers the process model used in Firefox OS including the b2g process, plugin container process, and hardware access. It also summarizes the Inter-Process Communication (IPC) mechanisms like IPDL, network APIs like XMLHttpRequest and WebSockets, as well as inter-app communication capabilities in Firefox OS like Web Activities and direct app connections.
This short document discusses HTML5 and localization. It questions who benefits from BML and emphasizes thinking globally rather than locally, while also noting the need to localize. The document ends by stating a belief that the internet should be public, open, and accessible.
17. Need feedback
• We need a feedback to our
bugzilla
(https://bugzilla.mozilla.org/) if
you know the slow web
application
• Of course, you can add my
email address
(m_kato@ga2.so-net.ne.jp)
to CC when you file a bug
18. References
• Get latest development version
• http://nightly.mozilla.org/
• About demos
• http://hacks.mozilla.org/
• Documents for HTML, CSS and JavaScript
• https://developer.mozilla.org/
• Kraken JavaScript Benchmark
• http://krakenbenchmark.mozilla.com/
