This is an excellent reminder of how much things have changed in the last 10 years in our space; a popular tools vendor can go query a massive source code repository and reach out proactively for transitioning deprecated functions.
Kudos to the jQuery team for the great attitude; and of course all hail github, but they know I feel that way since they charge my card every month. :)
I assume they found those github projects using code search. Code search may not be used a lot, but the people and projects using it have a large impact. Is there any way we can convince Google it's worth keeping it available?
I'm being picky I know, but wouldn't it just be easier to use something like:
If you haven't tried rails-behaviors, I recommend it. It's a modular, drop-in replacement for jquery_ujs, and I think @josh will update it shortly for 1.7
My recommendation would be to maintain dependency versions yourself, i.e. download the version of jQuery you want to use and //= require jquery in application.js - then grab a new version of jQuery whenever you want it updated
The gem is a very thin wrapper around jQuery, jQuery UI and jquery_ujs, which basically makes the files available for inclusion in your manifests, and adds a jQuery specific helper method for your tests.
I'm not really a developer so ignore if that's not possible / makes no sense.
1.css 14kb -250ms
engine.js 12kb 250ms
jquery 33kb 320ms ???
jquery1.js 13kb - 243ms
jquery2.js 14kb - 250ms
So my page open 100ms faster :P
I don't think you gain anything by splitting it in 2 files. It could happen if the browser downloads the 2 files in parallel, but it can make your page load actually worse because you do not have a guarantee of parallelism (there's a limit to how many resources you can download in parallel from the same domain and adding multiple domains is not without cost because of the extra DNS lookup, which is also a big problem on mobile phones) and you're also introducing eval().
If anything, a better hack would be to load it such that it does not block the page being loaded.
See a sample how it's done in this project: https://github.com/alexandru/crossdomain-requests-js/wiki/Us...
Get to coding ;)
And the way these bugs get fixed is by someone spending a lot of time to track them down. As the 1.7 blog post mentions, we definitely welcome any help we can get. We are all volunteers so we don't have the time to quickly track down and fix every bug.
In the triage process we put priority on fixing the worst bugs that affect the most people. I personally triaged both #9646 and #8205 so we could mark them as verified, but tracking down and solving older-IE problems can be torture given the crude stone debugging tools available in those environments. If you have a high threshold for pain, we could certainly use your help.
I had to work around this insidious creation http://bugs.jquery.com/ticket/8205
It creates a memory leak (it hit my getJSON calls) that slowly strangled one of my apps until it crashed the browser.
I list a lot of hours on that one...
This new release fixes the issue and I can confirm the fix works like a charm.
They've also improved event delegation performance by a factor of 2.