News for hackers. Stuff that matters.
Re:Why It's Time to Sunset jQuery by evadne on Sunday April 14, 2013 @01:10PM (#5547421)
It might make sense to cherry pick jQuery features and build your own jQuery — if you absolutely need it, and absolutely can’t carry the whole library. In other cases I think it’s mostly just bikeshedding.

jQuery is there to minimize surprises. Native API is magnitudes faster — yes. It is also divergent across browser runtimes. Then you code for special cases and test by hand, now you’re building your own jQuery.

Maybe we have better things to do.

Re:Why It's Time to Sunset jQuery by Turing_Machine on Sunday April 14, 2013 @01:55PM (#5547571)
"yes. It is also divergent across browser runtimes."

And likely to get more so, now that Google has forked WebKit.

Losing support for IE 6 (or whatever) is no big deal, but support for both Android and Mobile Safari is critical.

Re:Why It's Time to Sunset jQuery by recusancy on Sunday April 14, 2013 @01:22PM (#5547445)
IIRC jQuery 2.0 will have the option for custom builds.
Re:Why It's Time to Sunset jQuery by jugglinmike on Sunday April 14, 2013 @01:44PM (#5547527)
Re:Why It's Time to Sunset jQuery by evadne on Sunday April 14, 2013 @01:55PM (#5547570)
This is good. Thanks :D I’m thinking along the line of what jQuery UI did — offering ability to customize a version of jQuery you can download from the site.