3 ms·
Except: https://dmitriid.com/blog/2017/03/the-broken-promise-of-web-components/ https://dmitriid.com/blog/2017/03/the-broken-promise-of-web-...
by mikece 8y ago
Except: https://dmitriid.com/blog/2017/03/the-broken-promise-of-web-components/ https://dmitriid.com/blog/2017/03/the-broken-promise-of-web-...
- dmitriid 8y agoI'll need to update that with recent developments like: no one uses vanilla WebComponents, as they are unusable. Everybody uses any number of layers on top of them: Polymer, Angular, Stencil, whatever.
- littlethrowaway 8y agoI've been trying to understand why I would use WebComponents over vue/react. Like, if you're going to use a layer on top of WebComponents, why not use something like Vue anyway. Their single file components allow you to compose your templates together <my-widget>Some slot content</my-widget> etc.. I'm struggling to see the use of Web Components. And how easily it's going to be to compose WebComponents in with your custom frameworks' components, I wonder how easy that is going to be (e.g. passing props down to a web component). It seems that you'll still be better off just picking a framework for the next wee while anyway. Still, I'll look forward to your updated article ;)