Re:How to avoid rewriting your JavaScript application
by seangrogg on Thursday October 20, 2016 @08:18PM
(#12757290)
I think you're forgetting additional HTTP functionality, rudimentary animations, additional wrappers around existing JavaScript representation of DOM nodes, and a variety of other things that you'll never realistically used but thrown into all your applications for posterity. Because in the end, you had jQuery.
[ Parent
| on HN ]
Re:How to avoid rewriting your JavaScript application
by angry-hacker on Friday October 21, 2016 @04:40AM
(#12759025)
With http2 the additional request is not a problem.
If you don't use jquery, you don't care about old browsers/OS not supporting them either. Also, cdn+caching of the library.
Re:How to avoid rewriting your JavaScript application
by seangrogg on Saturday October 22, 2016 @11:23PM
(#12771720)
Bytes are bytes are bytes, http/2 or no. It's far less intensive to polyfill what features I actually am using than sending down all of jQuery, and that can still be minified, gzipped, cached, delivered via CDN, and cache-controlled and/or placed in the application cache via service workers (where available).
But I can understand that it's less about the user experience and more about the developer experience nowadays.