Because Chrome was supposed to be optimized to run Web applications, a crucial element would be the JavaScript engine, a "virtual machine" that runs Web application code. The ideal person to construct this was a Danish computer scientist named Lars Bak. In September 2006, after more than 20 years of nonstop labor designing virtual machines, Bak had been planning to take some time off to work on his farm outside Århus. Then Google called.
Bak set up a small team that originally worked from the farm, then moved to some offices at the local university. He understood that his mission was to provide a faster engine than in any previous browser. He called his team's part of the project "V8." "We decided we wanted to speed up JavaScript by a factor of 10, and we gave ourselves four months to do it," he says. A typical day for the Denmark team began between 7 and 8 am; they programmed constantly until 6 or 7 at night. The only break was for lunch, when they would wolf down food in five minutes and spend 20 minutes at the game console. "We are pretty damn good at Wii Tennis," Bak says.
They were also pretty good at writing a JavaScript engine. "We just did some benchmark runs today," Bak says a couple of weeks before the launch. Indeed, V8 processes JavaScript 10 times faster than Firefox or Safari. And how does it compare in those same benchmarks to the market-share leader, Microsoft's IE 7? Fifty-six times faster. "We sort of underestimated what we could do," Bak says.
Monday, September 22, 2008
Chrome as IE-Killer
Excellent article from Wired magazine on the subject of Chrome's birth and objectives. They really put some work into the thing.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
Please feel free to post a comment. You do need to be registered (somewhere) to post, but this shouldn't be a problem.