Of course, you're right Paul. The irony is that all the browsers that support CSS transitions/animations will also support things like querySelectorAll(), addEventListener(), etc. and are across the board much more uniform. Much of jQuery suddenly could be paired down into many, many fewer lines of code... and some of the jQuery APIs become obsolete entirely. Looking towards future compatibility, here's where I see the real JS library needs:
-object/class management (things like $.extend or other patterns)
-dynamic animations (although in many, many cases this should be being done with CSS transitions and animations that are triggered by toggling classes)
-simple selecting and modifying attributes and classes on DOM nodes (see above)
-custom event firing and listening
-UI widgets (with preference towards widgets that are smart enough to work on desktop and mobile i.e. they use transforms, transitions, and animations and have different styles depending on css media queries against screen size)
Replying to [comment:13 paul.irish]:
+0, I really want this functionality and want it in jQuery.. but it's a poor choice to use DOM based animation on transforms. They should always be animated with transitions. Dunno if there's a ticket for moving animate() to transitions but that's the one that needs to happen.