Re:Removing jQuery from GitHub.com frontend
by shams93 on Thursday July 26, 2018 @04:49AM
(#17616016)
Yeah actually I stead of so much focus on frameworks it's better to focus on better polyfill implementations. It's only a temporary issue in many cases but the larger web does move slowly and then stardards like web components sometimes take a deacde or more to be fully baked. Wasm based polyfill would enable more browser maker innovation and competition without leading to slow and bloared pages for all but one device.
[ Parent
| on HN ]
Re:Removing jQuery from GitHub.com frontend
by Spivak on Thursday July 26, 2018 @09:36PM
(#17622825)
What's the point of polyfilling a nice API when you could just have a nice API to start with which leverages native functions when present? They don't seem to be philosophically different.
Or stated differently, "jQuery is just a JS polyfill for browsers that don't support native jQuery yet."