Chrome speeds up web apps by compiling JavaScript in the background
Google: Under-the-hood change helps Web apps on Chrome — Google has taught Chrome how to walk and chew gum at the same time. — The newest Chrome beta version, 33, includes a feature called concurrent compilation …
Context & Ripple Effects
Chrome's pitch has been speed since its 2009 debut, when Google framed the browser itself as the thing to optimize in its first beta announcement. The 2011 push added graphics muscle for richer web apps in the 'dash of speed, 3D and apps' release, and that same year Google began wiring app-platform machinery into the browser with Android-style Web Intents. Concurrent compilation in the Chrome 33 beta is the next link in that chain: JavaScript gets compiled on background threads while the page keeps loading.
The pickup was unusually broad for an under-the-hood change — the Chromium Blog post traveled to The Register, The Next Web, SlashGear, HEXUS, Softpedia and CNET within a day — because it lands mid-flight in Google's campaign to position the browser as an application platform, not a document viewer.
First-order effects
- Developers of JavaScript-heavy web apps get faster startup in Chrome 33 beta with no code changes, since compilation moves off the main thread while pages load.
- Google's browser gains a measurable responsiveness edge over rival engines at zero cost to users, pressuring Firefox and Internet Explorer teams to answer with their own pipeline work.
Second-order effects
- Narrower web-versus-native performance gaps strengthen the case for Chrome OS deployments like the VMware Horizon DaaS partnership announced this week, which streams Windows desktops into the browser and competes on how well Chrome runs heavy applications.
- As compile time stops being a user-visible cost, web app frameworks grow more ambitious, pulling tooling vendors and enterprise buyers toward browser-delivered software over installed clients.
Third-order effects
- Background compilation treats the browser engine as an operating-system-class runtime, continuing the trajectory Google started with Speed Tracer's developer tooling in 2009 — the browser becomes the platform layer where app performance wars are fought.
- If every major engine converges on concurrent pipelines, differentiation shifts from raw JavaScript speed to the surrounding platform surface — intents, packaged apps, desktop streaming — which is where Google has been investing since 2011.
The trend: Browser makers are shifting competition from page rendering to runtime engineering, turning the engine into the performance-critical foundation for web-delivered applications.