Web Components Guide
webcomponents.guide
Web Components Guide
1–8 of 8 posts
Re: Web Components Guide
#2Excited to see where these go, especially if they can minimize the need for bespoke JS. Still, not sure how they'll scale or get adopted.
Re: Web Components Guide
#3Unfortunely given that the cool kids React is anti-Web Components, this will hardly get sorted out (Vue and Angular support Web Components out of the box).
Re: Web Components Guide
#4Unfortunely given that the cool kids React is anti-Web Components, this will hardly get sorted out (Vue and Angular support Web Components out of the box).
There's hope for React yet: https://github.com/facebook/react/issues/11347
Re: Web Components Guide
#5Re: Web Components Guide
#6Unfortunely given that the cool kids React is anti-Web Components, this will hardly get sorted out (Vue and Angular support Web Components out of the box).
There's hope for React yet: https://github.com/facebook/react/issues/11347
When someone from the Chrome team actually had to write the code for them. I don’t think the React team themselves cares about interoperability at all however.
Re: Web Components Guide
#7Earlier quoted context omitted.
There's hope for React yet: https://github.com/facebook/react/issues/11347
When someone from the Chrome team actually had to write the code for them. I don’t think the React team themselves cares about interoperability at all however.
If they have no use for it, why would they?
Re: Web Components Guide
#8Earlier quoted context omitted.
When someone from the Chrome team actually had to write the code for them. I don’t think the React team themselves cares about interoperability at all however.
If they have no use for it, why would they?
Because it’s a large open source project and it’s important to have interoperability with the rest of the platform.