Yep, with jQuery in the core it's probably best to just bundle it. There is another issue with the code loading and stuff - making JS libraries call a callback function when they load and all the functionality to be there instead of relying on browser to block everything until library is loaded. This is quite advance thing considering that all the code will have to be converted to this model, but it will allow for much better performance when implemented. Still it's probably "Phase 5" kind of optimization, but it can bring really good results considering JS being the biggest blocker.
More on the topic is on Steve Souders' blog: http://www.stevesouders.com/blog/2008/12/27/coupling-async-scripts/ Thank you, Sergey -- Sergey Chernyshev http://www.sergeychernyshev.com/ On Wed, Apr 22, 2009 at 12:42 PM, Brion Vibber <br...@wikimedia.org> wrote: > On 4/22/09 9:33 AM, Sergey Chernyshev wrote: > > Exactly because this is the kind of requests we're going to get, I think > it > > makes sense not to have any library bundled by default, but have a > > centralized handling for libraries, e.g. one extension asks for latest > > jQuery and latest YUI and MW loads them, another extension asks for > jQuery > > only and so on. > > Considering we want core code to be able to use jQuery, I think the case > for bundling it is pretty strong. :) > > -- brion > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
