

We reported last month that over half the world’s developers will be working on software as a service projects in 2009, so the trend is definitely moving in that direction. The reason has to do with the slow transition to cloud-based web applications.

However whether the current fastest engine is Google’s V8, Mozilla’s TraceMonkey, Apple’s SquirrelFish, Microsoft’s JScript, or Opera’s Futhark the battle is an important one. The game of one-upmanship has been going on for awhile now, and it’s not easy to stay on top of who has the current fastest JavaScript engine - especially since different benchmarks often yield vastly different results. One of the most important fronts in the fight for web browser supremacy is the battle for JavaScript engine speed.
