That's generally a bad idea. Think about the different versions of jQuery that come out right after a browser version does. On top of this, what if you want to use a different library. How would we choose to use jQuery as opposed to Dojo or Prototype, etc.
I think the way things are right now, it works just fine with one small exception: I got spoiled by jQuery. I do everything in it. I don't mean just web projects, I mean I do command line stuff with it. I have Firebug installed and so every time I end up on a website where I need to extract some information out of it, I fire up Firebug and do something along the lines of this:
It would really be ideal if Firebug shipped with jQuery built in, or at least have an option. This way I wouldn't have to do this every time I want to do some DOM-fu. Come to think of it, I should make this I should publish this bookmarklet.
No, you don't. A lot of people think that this would be a great win for any JavaScript library, but I guarantee that every single library author would disagree.
The last thing we want to do is give browser vendors more control over any part of the process.
As we have discussed yesterday in the IE9 post, the bottleneck is not JavaScript execution anymore, it's DOM manipulation. Having jQuery "precompiled" wouldn't help all. Browsers need faster DOM interfaces.
