JQuery 1.4 released

They're using the Google Closure compiler as their minifier now.<p>Resig in this presentation (warning: video autoplay), in response to the last question, said that while it's slick if you simply throw jquery into it you'll just get broken javascript out: <a href="http://developer.yahoo.com/yui/theater/video.php?v=resig-testing" rel="nofollow">http://developer.yahoo.com/yui/theater/video.php?v=resig-tes...</a> I wonder what has changed?<p>(Maybe just not running it in advanced mode; at any rate, they're reporting a 13% decrease in file size: <a href="http://github.com/jquery/jquery/commit/3fd62eae9df3159fc238a515bb748140a942313d" rel="nofollow">http://github.com/jquery/jquery/commit/3fd62eae9df3159fc238a...</a>)

The performance boost is great but I think the thing I'm most excited about is "All Events Can Be Live Events". Thanks jQuery team!

What is up with the stacked bar charts used to show performance improvements in various css/html features? I can't really think of a seeing a more useless/opaque chart in quite a while. They make it impossible to do effective 1.3 -&#62; 1.4 comparisons for specific browsers and since no one is running on all five browsers at once the weird style chosen doesn't even coherently communicate an overall point.

I've been a Prototype user for a few years now. I've always kept an eye on jQuery, but my knowledge of it is incredibly shallow. I have to say, I was shocked when I saw that they added the "proxy" method. This description makes it sound exactly like "bind" method in Prototype. Is that a valid comparison? If so, why did it take so long for this to appear in jQuery? At this point, I don't think I could write a snippet of javascript without relying on that method.

Live Q&#38;A at 4pm EST. <a href="http://ustream.tv/channel/14-days-of-jquery" rel="nofollow">http://ustream.tv/channel/14-days-of-jquery</a>

Making jquery.browser engine-centric is a nice touch, especially now that webkit based browsers are breeding like rabbits.

Those graphs performance graphs per browser are very confusing. I'm guessing that the individual colors show the time taken per browser, but the fact that it's stacked makes me think that the slowest ones are on top and the fastest ones are on bottom, but that can't be right since IE6 is always second from the bottom.

Congratulations to the jQuery team for the optimizations in 1.4. It's hard to believe such gains were made over 1.3 considering how significant <i>that</i> change was over 1.2.

This is cool. remove() was a bottleneck for my app, but a constant-fraction speedup won't be enough to fix it. I'll have to dig in and see if it actually works differently now.

Just upgraded <a href="http://wasitup.com" rel="nofollow">http://wasitup.com</a> to jQuery 1.4 without issues.

Fixed a jquery 1.4 alpha related bug over at <a href="http://twidl.it" rel="nofollow">http://twidl.it</a> for our reTwidl function! In the nick of time too (we encountered bug yesterday). Thanks Jquery team!

Sounds awesome. I'm going to have to update ASAP.<p>Great work - coding javascript is seriously easier than it was before JQuery came along.

I found the page linked under the words "reduce the complexity" ( <a href="http://ejohn.org/blog/function-call-profiling/" rel="nofollow">http://ejohn.org/blog/function-call-profiling/</a> ) a rather exemplary tale of profile-and-optimize.

Consistently crashes Chrome 4.0.266.0 on Ubuntu

Congrats to the jQuery team!