I wish they focused more on jquery-ui, as I find that a bit lacking at the moment.

New Selector Engine (Sizzle: http://github.com/jeresig/sizzle/tree/master). Much faster than previous engine, going to be in many of the major libraries.

No more browser sniffing (currently being discussed here: http://www.reddit.com/r/programming/comments/7l2mr/jquery_re...).

.closest() method - extremely useful for event delegation.

    // Returns this or closest ancestor that matches selector
    $(this).closest("div");

    // Will handle clicks on all elements that match selector
    // even if new ones are added later
    $("#foo > div").live("click", someFn);

.hide()/.show() rewrite - 50% - 200% faster.

.append/prepend/before/after rewrite - 10-15x faster.

While the biggest feature of this release is performance, the new event delegation methods are going to be super-useful.

As to jQuery UI - there are multiple teams within the jQuery project - the core jQuery team works on the jQuery library and the jQuery UI team works on jQuery UI. In their last update (about a week ago) the UI team said that UI 1.6 final was going to be out before the end of the month.

We don't have that luxury with CSS. There's no universal way for all browsers to let JavaScript know when a new element has been added to the page - or that it's been moved. There's the W3C DOM mutation events but they aren't implemented everywhere.

More info: http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-e...

Thanks for your quick response.

Hquery: Uses pure HTML as "template" for rendering views a Hpricot sequence (in the .hquery counter-part file) is executed to modify the pure HTML and the resulting HTML is output to the browser.

Right now you can set HTTP headers in jQuery like so:

    $.ajax({
      beforeSend: function(xhr){
        xhr.setRequestHeader("Accept","application/json");
      },
      ... other options ...
    });

And it would really be nice if the "simple" ajax functions also allowed doing something if there was an error.

Check out getResponseHeader() if you are so inclined.

As for the errors, there are many ways to check for "ajax" errors, for one thing you can check the status or statusText property.

I know how to detect errors, that was hardly my point. I was suggesting an improvement, not tech support.

http://www.json.org/js.html

// In the third stage we use the eval function to compile the text into a

// JavaScript structure. The '{' operator is subject to a syntactic ambiguity

// in JavaScript: it can begin a block or an object literal. We wrap the text

// in parens to eliminate the ambiguity.

// This is a function that can parse a JSON text, producing a JavaScript

// data structure. It is a simple, recursive descent parser. It does not use

// eval or regular expressions, so it can be used as a model for implementing

// a JSON parser in other languages.