You guys are doing awesome work. Thank you.
Would love to see some benchmarks!
Using Chrome 21.0.1180.57 on OSX.
I think it's still worth the upgrade.
1.7.2 4,123 ops/s 242 microseconds/op
1.8.0 4,061 ops/s 246 microseconds/op
In practical terms, the speedup in custom selectors is probably the most important, since they are so slow.
As I mentioned in another comment, increasing performance for ID selection (which is already much, much faster than other types) at the expense of other types makes for sexy benchmarks, but is less than stellar in the real world.
Making a huge increase in one type of selector for the sake of an insignificant decrease in another selector is an obvious win.
Now someone comes along and makes B 10x faster while making A 2% slower (which is what the numbers above seem to show for the class selector). Now your execution time is 102.1t, which happens to be larger than 101t.
The upshot of all this is that if use frequencies are equal, performance improvements for slow things (even small ones) are worth a lot more than performance improvements for things that are already fast. Now obviously you have to weight by frequency of use, which may differ for different API consumers.
There's only one case in which speeding up already-fast stuff at the cost of slow stuff getting even slower is an obvious win regardless of use frequency: benchmarks averaged using geometric means. Which is the most popular averaging method, of course: see Dromaeo, V8 benchmark, PeaceKeeper, etc.
Do you mind illustrating how the net performance of jQuery has been reduced with the release of 1.8?
Considering that they have custom download options for jQuery UI and recently added a tool for jQuery Mobile (http://jquerymobile.com/download-builder/), I expect it won't be many more months before they add one to jquery.com.
Does include an online builder at: http://jquip.ubixar.com/
It's also the only version of jQuery to support Google Closure's advanced compilation mode.
Anyway, I'm happy to see jQuery moving into a smaller more modular code-base.
Does this mean I can apply rounded corners via jquery css without having to write 4 separate css properties for each browser?
Thought I'd share this because this was giving me the shits.
Is it just me, or is that overly passive-aggressive for a release announcement?
Size reduction wasn’t our primary goal in this version,
but we felt it was important to hold the line on code
growth, and we definitely achieved that.
TL & DR for the patch:
- some internal rewrite
- some small fixes
- smaller code size