3 ms·
I don’t think the crossover is bound to happen. With Web Components the browsers went all-in on ideas about components that made sense in the early 2010s, but t
by Uehreka 3y ago
I don’t think the crossover is bound to happen. With Web Components the browsers went all-in on ideas about components that made sense in the early 2010s, but then couldn’t evolve them because they had already standardized. In practice most component libraries don’t use Web Components under the hood (yes, I know Angular does if you tell it to, in practice I’ve never seen anyone use this) and aren’t polyfills. The main framework that worked that way (Polymer) has been out of use for years.
- sergiosgc 3y ago> In practice most component libraries don’t use Web Components under the hood (...) Look at Shoelace's code. It's just Web Components, coded in Typescript on top of lit.dev. It's about as easy to write as Vue. > and aren’t polyfills I know, hence the quotes on my text.
- niutech 3y agoWeb Components are still relevant, see e.g. Lit Element, Stencil.
- Uehreka 3y agoI’ve heard pf Lit Element, I have never seen it used in production. I work for an agency, so I see several new frontends every year, and almost all of them are Angular, React or Vue. I know that these other frameworks exist and what their deals are because I listen to ShopTalkShow and so on, but I don’t think they’re that big in terms of what people are using in the field.