Slashdot Mirror

← Back to Stories (view on slashdot.org)

The Future of Google Chrome

Posted by CmdrTaco on from the didn't-safari-just-poach-their-best-features dept.

TRNick writes "Lars Bak, who heads up development of Google Chrome's cornerstone javascript engine, talks about why Google is so focused on in-browser javascript performance, the role Chrome has played in driving up javascript performance in other browsers, and why it's taking so long to introduce support for third-party extensions. 'The web is becoming an integral part of the computer and the basic distinction between the OS and the browser doesn't matter very much any more,' he says."

2 of 294 comments (clear)

  1. The whole point of Chrome by LeDopore · · Score: 5, Insightful

    is that its future per se doesn't matter.

    What Google cares about is that there is a least one standards-compliant browser out there with fast javascript. Sure Google might have a slight preference for people using Chrome over another browser with fast javascript (like, say, Safari), but what really matters to them is that they are able to deliver web apps that are fast enough to be reasonable competitors to traditional desktop apps.

    Chrome is a combination insurance policy/open-source soapbox whose purpose is to make sure that Google apps (and other web apps) will always have a browser to run on.

    --
    Expected time to finish is 1 hour and 60 minutes.
  2. Re:I know the future... by Ninnle+Labs,+LLC · · Score: 5, Insightful

    Because not everyone in the world is a programmer?