- From: Hallvord R. M. Steen <hallvord@opera.com>
- Date: Mon, 18 Oct 2010 13:44:35 +0900
- To: "Tony Gentilcore" <tonyg@chromium.org>, "Henri Sivonen" <hsivonen@iki.fi>
- Cc: "Adam Barth" <abarth@webkit.org>, "public html" <public-html@w3.org>
On Fri, 15 Oct 2010 16:12:51 +0900, Henri Sivonen <hsivonen@iki.fi> wrote: >> In my >> experience working on Google web properties, developers turn to >> script-inserted scripts only when they want a performance gain from >> async behavior. Hi Tony, thanks for joining the discussion :). The potential performance gain from async behaviour is actually the result of three different behaviours: 1. script downloading not blocking parsing 2. several scripts downloading in paralell (also possibly parser-inserted scripts, as a consequence of first point) 3. executing any script that is done downloading without waiting for earlier scripts Which of those behaviours do you think is more important in the scenarios you have observed? Google properties (at least when I look at their publicly deployed code) typically load one single huge JS file. Of course I have to way to check how the code looks when developers are working on it ;) If they load JS as one single file, the performance gain they would be looking for comes from avoid it blocking the parser, not from running it as fast as possible relative to other scripts, which is what we're discussing at the moment.. -- Hallvord R. M. Steen, Core Tester, Opera Software http://www.opera.com http://my.opera.com/hallvors/
Received on Monday, 18 October 2010 04:44:52 UTC