This is just one example. But yeah, it’s larger.
Web Components still require polyfills. The argument that these big companies ship them is fine, if you have the same user base as those companies and can alienate the same set of browser users.
I still have to support IE 11 for example. caniuse.com/#search=Web%20components
I mean, if they work for you, and your happy with the framework. Congrats. I don’t need to keep going against every point you want to try and dismiss. It’s simple. Moving CSS and HTML into JS is thick client still. Might be lighter weight than a virtual dom, but it has ramifications. I have to support a wider range of users than you, and hence can’t use the features without polyfills.
So like I said before, I don’t feel we are ready for mass adoptions. Most websites can’t abandon IE11 or Edge. And I won’t use a collection of polyfills just so I can develop with a framework. Why punish the user. They don’t care that your using web components. They just want the site to be fast and work. So use the technology that does that the best. For me, that is Svelte or just native HTML, CSS and JS.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.