W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > December 2010

[Bug 11402] One problem of todays JavaScript libraries is, that the client has to download the same library over and over again, while visiting multiple sites. One could use services like Google Libraries API for a central location, but that introduces new points of

From: <bugzilla@jessica.w3.org>
Date: Thu, 02 Dec 2010 18:07:39 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PODZD-00039S-G5@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11402

--- Comment #10 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2010-12-02 18:07:38 UTC ---
(In reply to comment #9)
> The problem is that once you add a library to the browser you can *never remove
> it*.  It's now just part of the exposed API.

Not as long as people provide working src="".  Of course, if all browsers agree
on library versions to bundle, people will leave out src="" or point it
someplace that doesn't work.

On the other hand, if all browsers agree byte-for-byte on what library versions
to bundle, that includes the OS default browser, so browsers can just use the
OS versions.  OSes can afford to package a handful more libraries every year
indefinitely, I imagine.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 2 December 2010 18:07:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:35 UTC