But I'm not sure how I feel about it. There's nothing wrong with the current way and the guy admits that he likes this way simply because it cleans up the code. But that's a subjective thing, I have no problem reading code written in the usual way.

But like I said, he fully admits this.

Sometimes I like to use an anonymous function for the event handler, do some things pertaining to that and then call another function for other reasons. With this method I don't see how you could do that so I'd have to fall back on the traditional method.

Then he mentions bloat but I'm not sure what this actually saves you. Keeping in mind the amount of code needed to get this to work, there has to be some threshold with number of event handlers used before this starts saving lines of code. His extension code is about 50 lines, which I'm sure can be squeezed down. But that might be considered a lot of code for one specific use.

If you don't cross the mentioned event handler threshold, or don't even use it at all, then the included code is actually causing bloat in the long run. That's often one of the main reasons for not using a framework over writing your own code because of framework features that you don't use. But then again, this is an extension so you just load it up on the needed project and use it as required.

In the comments there were suggestions of putting this into jQuery itself, I think that would be a mistake.

Im not sure if I understand what you mean, but what happens when you do $.lazy('jquery.elastic.js','elastic'); is extending jquery with a function called elastic.

Then when you call that function by doing ie $('.foo').elastic(); lazy will be loading up all the dependencies first css, then js and then the actual plugin. And then overwrite the function elastic with the the actual plugin. And when that is done (loaded and inserted to the html page) its going to run $('.foo').elastic(); again..which is now the plugin inside jquery.elastic.js and completely separated from lazy.

You wont be using $.lazy() to load up your plugins. The loading will be done when you call for the actual plugins ie $.elastic();

Haven't tried with extremely large libraries and plugins.. but handles Jquery UI with both css and js dependencies as expected.