- From: Joe Pea <notifications@github.com>
- Date: Mon, 25 Jul 2022 16:47:10 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 25 July 2022 23:47:23 UTC
It seems like this spec will have to lead to browsers allowing native templating to be faster and more space efficient than frameworks in benchmarks (f.e. see [js-framework-benchmark](https://krausest.github.io/js-framework-benchmark/current.html)) or we'll end with something that people won't use; they'll just use the frameworks (which already have good DX, f.e. JSX with full type support in TypeScript, along with compile-time optimization thanks to new tools like [Solid.js](https://solidjs.com)). A solution would need to be _as easy, or easier_ than these frameworks for it to be really adoptable. If people are going to end up writing frameworks on top of DOM Parts (or related APIs), then end users will ultimately be using frameworks, and will end up still choosing whatever works best (whether built in or not). Has this been given consideration? -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/704#issuecomment-1194780494 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/704/1194780494@github.com>
Received on Monday, 25 July 2022 23:47:23 UTC