“jQuery is not need anymore with modern browsers.”
Bull. Shit.
This document proves why, and is written by the same guy that is now pushing this “you don’t want jQuery!” stuff.
https://docs.google.com/document/d/1LPaPA30bLUB_publLIMF0Rlh...
Bull. Shit.
This document proves why, and is written by the same guy that is now pushing this “you don’t want jQuery!” stuff.
https://docs.google.com/document/d/1LPaPA30bLUB_publLIMF0Rlh...
You don't "need" jQuery, but you might not-not need jQuery unless you do something about those bugs.
yell.com mobile site removed jQuery from their codebase, and used that list during the process. Looking at each bug, does it affect them, yes/no. If yes, code around it.
I'm a jQuery fan, but sometimes you might not need jQuery, but sometimes you might not-not need jQuery
> Bull. Shit.
Depends on the target environment(s). If you only want to support evergreen browsers then there is no reason you need jQuery; you're going to have the native DOM APIs and you don't care about compatability.
jQuery's big win is two fold, in my opinion. One it has awesome, chain-able syntax and two (most important) it has awesome backwards compatibility with terrible browsers. If you don't need two then is one worth bringing in another dependency? Maybe or maybe not.
False.
Read the first sentence of the document I linked to.
“…developers should be aware that ditching libraries, like jQuery, can easily require large amounts of research on their end to avoid bugs (even in modern browsers).”
Bear in mind it’s Paul Irish who wrote that.
> Read the first sentence of the document I linked to.
Oh I did. Look through many of the bugs they outline; many are incredibly minor and inconsequential unless you're doing things related (or semi related) to supporting older browsers.
> Bear in mind it’s Paul Irish who wrote that.
Yup; I don't see his posts being quite in conflict like many here seem to think. Plus his opinion has probably evolved overtime anyway (he wrote that document a year and a half ago).