3 ms·
The spec constantly evolves. At some point, there will be web components "v2" and coding "regular" web components will be outdated. As the spec evolves, browser
by joshribakoff 9y ago
The spec constantly evolves. At some point, there will be web components "v2" and coding "regular" web components will be outdated. As the spec evolves, browsers will evolve at different paces & implement things differently. Such is the reality of cross platform development. The only constant is change itself. To deal with it we use tools like polyfills, libs, and frameworks.
- pjmlp 9y agoThat matters very little because our components are wrapped in ASP.NET, Spring, JEE components. For the user of use components the difference will be quite thin, if at all.
- joshribakoff 9y agoRight, those things fall into the category of tools libs & frameworks. Like Carl Sagan says if you want to make an apple pie from scratch you have to first invent the universe. There's always going to be change and need to support backwards compatibility, so polyfills libraries & frameworks likely aren't going away anytime soon, even after web components are widely supported.