3 ms·
> why would anyone want to subject themselves to framework lock-in when you can have components that are portable across frameworks? what are the arguments agai
by troupo 3y ago
> why would anyone want to subject themselves to framework lock-in when you can have components that are portable across frameworks? what are the arguments against?
https://twitter.com/Rich_Harris/status/1198332398561353728 https://twitter.com/Rich_Harris/status/1198332398561353728
None of these are solved, or will be adequately solved in a forseeable future.
Some of these will be addressed by ~20 new JS-only specs in the various states of "not started" https://w3c.github.io/webcomponents-cg/2022.html https://w3c.github.io/webcomponents-cg/2022.html
Literally none of the major (or even emergent) frameworks have these issues, or a chance of running into these issues.
- woodrowbarlow 3y agothank you; these are good, specific examples. #2: maybe i'm misunderstanding, but i think frameworks can implement SSR on top of vanilla components, for instance in Lit: https://lit.dev/docs/ssr/overview/ https://lit.dev/docs/ssr/overview/
- troupo 3y agoIf you need framework-specific solutions to do SSR for web components... they are no better than existing solutions without them. Lit solution also lists a lot of caveats including things like "only Lit elements using Shadow DOM can be SSR'ed" and "element registry needs to be solve for interop with other custom elements" (that is, there's an issue on the standards level)
- troupo 3y agoI've written a more extended response in a different thread here: https://news.ycombinator.com/item?id=37158524 https://news.ycombinator.com/item?id=37158524