 Well welcome. I'm so excited about what we have in store for jQuery 1.8 and sizzle First up, let's talk about performance Many things stayed the same, but We did get a performance increase in filtering and matching which means oh Excuse me. Sorry Try to speak into the mic here What I've got here is a comparison of 172 versus 1.8 1.8 is the green First one there is event trigger when you do event delegation it needs to filter all of the elements all of the descendants and Find matches and then run a callback on those elements. This isn't a comparison of These four different types of matches. It's just 172 versus 1.8 Event triggering simple matches complex matches as a small performance increase about 5% across the board Our biggest performance increase is in element rooted ID matches, which is JQuery something dot find ID Performance of that selection improved by about 300 percent. So I'll do a quick summary of performance here Matching and filtering as I said improved just leave about 5 to 10 percent If you remember quick is in event.js Which was talked about the last conference by Dave In his rewrite it was actually moved to sizzle so that we can get the same advantage Is in filtering for all selections not just in an event delegation Simple selectors we improved those shortcuts and added them to everything not They were previously Just in browsers with query selector all now they're in IE six seven eight You'll get a little bit better performance in the simple selectors as I said element rooted ID selections and And shorter code paths to query selector all and match selector we have Excellent code path here all of the performance tests that I did Showed that we have very competitive Small code path to get to these native methods So that's performance. Let's talk about bugs Yeah, we don't actually have any bugs Thank you To lowercase not we're good was actually a bug ticket that we received sometime last year Yeah, we never fixed that Okay, there were bugs We improved qsa match selector bug detection which means We detect When it's gonna fail before we actually run it all browsers even Chrome Safari Firefox have bugs and query selector all so We figure out if it's gonna fail and if it's going to fail skip query selector all and and Make sure it's right. So bypasses that here are some examples Class equal empty string checked won't return selected options in Several browsers and of course The infamous at properties in I8 Yeah, I have a long-standing relationship with the attributes We fixed a bug in with combinators Which means tilde plus sign? Descendants space When using multiple of those they were weren't always getting every result. So we fixed that Element root query selector all with divisions what I mean by divisions is comma It wasn't Respecting your context when you add to the comma Unicode validation we'll get into that too much and several little edge cases So What's coming up next you aren't prepared by the way? Everything that I've told you so far might actually change. I did rewrite sizzle Yes, we're adding all the bugs back That's the idea I Might rewrite it again. Actually. I'm in the process of rewriting it again, but if it's not better. I won't commit it I'll I'll say that I Won't get in that too much After 1.8 though, we're gonna add some more CSS 3 support. There are a few selectors that we don't support Particularly of type nth of type last of type and target root So some pretty uncommon ones, but still ones we are considering supporting even more selector validation and Of course there there are still bugs to be fixed Despite what Dave says So We need your help with that sizzle is on github under the jQuery organization and Issues are also on github I'll be migrating all of the bugs from the jQuery bug site over to sizzle There aren't many but That aren't already in issues So pick an issue and dig in Discussion for sizzle is still in jQuery dev. There's no special IRC channel and There's a stale Sizzle Google group that I'd like to see pick up some more activity Same style guide Same development workflow sizzle doesn't use grunt So and it will run lint for you as you develop and if you have any questions you can always ask me I'm in IRC I'm on Twitter and github as Timmy will And that's it Next up we got