3 ms·
The big benefit (once Firefox and EDGE support them) is in not needing to download 132K of Javascript for basic platform functionality. It's much like JQuery.
by nostrademons 9y ago
The big benefit (once Firefox and EDGE support them) is in not needing to download 132K of Javascript for basic platform functionality.
It's much like JQuery. It was very much necessary when it came out in 2006. But then browsers got querySelectorAll, classList, uniform event handling, uniform dimensions, fetch, animations, transitions, data-attributes, and basically all the other functionality in JQuery.
The JQuery API is still more convenient in many cases, and several loyalists are still like "You'll pry JQuery out of my cold, dead fingers." But they build worse sites - for the same functionality, their sites are slower, take longer to load, and have more things that can go wrong. The market usually flushes such loyalists out eventually, and we may see a similar situation with React/Vue/Angular when components are standardized across browsers.
- bastawhiz 9y agoI don't think I've ever seen a Polymer-powered page of any substance use less than 132kb of JavaScript. File size is really not a good reason to choose web components, especially when you consider the things you need to do to actually work efficiently with web components once you have them.
- coldtea 9y ago>The big benefit (once Firefox and EDGE support them) is in not needing to download 132K of Javascript for basic platform functionality. If that's the big benefit, then it will be increasingly irrelevant (assuming its not already), including on the mobile space. Especially since those 132K (for React, Angular, and the like) are not "basic platform functionality" but give tons of things that Web Components do not.
- talmand 9y ago>> for the same functionality, their sites are slower, take longer to load, and have more things that can go wrong I would like to see sources supporting these claims, please.