Web Components Guide

Posted by Keithamus on Monday January 09, 2023 @01:05PM
from the webcomponents.guide dept.

https://webcomponents.guide/blog/introducing-webcomponents-guide/

( 7 comments | 4 points | on HN )

Re:Web Components Guide by paulryanrogers on Monday January 09, 2023 @08:52PM (#34319307)

Excited 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.

[ Parent | on HN ]

Re:Web Components Guide by pjmlp on Tuesday January 10, 2023 @02:55AM (#34321805)

Unfortunely 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).

[ Parent | on HN ]

Re:Web Components Guide by Keithamus on Tuesday January 10, 2023 @05:31AM (#34322807)

There's hope for React yet: https://github.com/facebook/react/issues/11347

[ Parent | on HN ]

Re:Web Components Guide by pjmlp on Tuesday January 10, 2023 @05:35AM (#34322827)

Thanks for the heads up.

[ Parent | on HN ]

Re:Web Components Guide by mhoad on Tuesday January 10, 2023 @01:29PM (#34329251)

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.

[ Parent | on HN ]

Re:Web Components Guide by asalahli on Wednesday January 11, 2023 @08:51AM (#34338411)

If they have no use for it, why would they?

[ Parent | on HN ]

Re:Web Components Guide by mhoad on Thursday January 12, 2023 @01:35AM (#34349968)

Because it’s a large open source project and it’s important to have interoperability with the rest of the platform.

[ Parent | on HN ]