3 ms·
The use case I'm most excited about for Web Components are those producing reusable components (like YouTube embeds you describe). Building the same components
by yesimahuman 9y ago
The use case I'm most excited about for Web Components are those producing reusable components (like YouTube embeds you describe). Building the same components for different frameworks no longer makes sense when you consider that you could publish a web component instead that would work out of the box with most modern frontend frameworks. I'm incredibly bullish on them now, and we're going to be turning Ionic components into WC's so we can work with all frameworks people want to use (because, there hasn't been one single framework that has "won" the frontend market)
- dbbk 9y agoWould YouTube embeds ever move to web components from iframes though? Seems like iframes would actually be more suitable for this use case.
- yesimahuman 9y agoIf they wanted to use iframes still, they would just have that inside the component. Then, you wouldn't need any initializing code really. Admittedly, not a huge win because it's pretty small embed code as it is.
- my_ghola 9y ago> consider that you could publish a web component Is there any place you can go look at Web Components built by others and contribute your own? plus a package manager to include them easily in your projects would be the best way for them to come to light.
- Spone 9y agohttps://www.webcomponents.org/publish https://www.webcomponents.org/publish