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

Re: Executing script-inserted external scripts in insertion order

From: Getify <getify@gmail.com>
Date: Tue, 12 Oct 2010 12:52:09 -0500
Message-ID: <10D4DDBD202F4A13AFE284B2BDBFC0B4@spartacus>
To: "public html" <public-html@w3.org>
> ...but all my addons and other libraries?
> Not a chance.  I download them once and that's it, unless I have a
> problem with the library and my searching leads me to discover a new
> version.

I think this definitely constitutes the majority use-case. But I think it's 
fine and reliable in support of my argument because the corollary assertion 
is that you regularly do due-diligence to make sure that your site/app works 
fine in all the latest browser versions. If a browser releases a change that 
breaks LABjs, and LABjs is subsequently updated to address any problems, but 
you haven't yet seen or known about this LABjs update.. you will hopefully 
soon notice your site break, and can hopefully determine quickly it's LABjs 
related -- so, it's not a far stretch that you'll end up finding out there's 
a new version of LABjs that will address your problem, which you can then 
easily update (more easily and less risky than a jQuery update because of 
much more targeted/focused functionality). That's what Git repo history, 
readme's, change-logs, release notes, etc are all intended to do... inform 
users of what the update fixes.

Received on Tuesday, 12 October 2010 17:52:49 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:05 UTC