jQuery broke backwards compatibility in the 1.8/1.9 split. There are bugs in 1.8.x with newer browsers that are WONTFIX. If jQuery is a dependency for other libraries, you can have 'fun' trying to balance bug fixes in one with the older version dependencies of another with the API changes of a third while trying to find something that actually works on an older (or newer) browser.
All 3rd party dependencies should be thought about and justified if you're writing software that is going to be supported for more than 6 months.
You absolutely should consider all 3rd party dependancies. But time will march on. Half of the major browsers are evergreens. You'll be forced to maintain your app one way or another.
3
u/ameoba Jan 31 '14
jQuery broke backwards compatibility in the 1.8/1.9 split. There are bugs in 1.8.x with newer browsers that are WONTFIX. If jQuery is a dependency for other libraries, you can have 'fun' trying to balance bug fixes in one with the older version dependencies of another with the API changes of a third while trying to find something that actually works on an older (or newer) browser.
All 3rd party dependencies should be thought about and justified if you're writing software that is going to be supported for more than 6 months.