News for hackers. Stuff that matters.
Re:Making Web Components Work by spankalee on Tuesday June 12, 2018 @03:57PM (#17297383)
This is exactly what Web Components already do. Web Components are just HTML elements, and generally usable in any framework or with no framework.
Re:Making Web Components Work by mikece on Tuesday June 12, 2018 @04:01PM (#17297430)
Oh -- awesome! I've been focused on back-end and mobile the past few years. I guess it's time to dive into Web Components!
Re:Making Web Components Work by themacguffinman on Tuesday June 12, 2018 @07:57PM (#17299143)
Re:Making Web Components Work by mikece on Tuesday June 12, 2018 @05:14PM (#17298074)
Re:Making Web Components Work by dmitriid on Wednesday June 13, 2018 @02:22AM (#17300705)
I'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.
Re:Making Web Components Work by littlethrowaway on Saturday June 16, 2018 @08:43PM (#17330317)
I'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 ;)