HN2new | past | comments | ask | show | jobs | submitlogin

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.



"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.


IIRC jQuery 2.0 will have the option for custom builds.



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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: