Yes, I know Lit exists, and yes it's fast. But I think you're missing the point.
I'm not talking about one JS implementation vs another or if JS solutions are fast enough from the end user perspective.
The fastest JS solution (VDOM, Svelte, Lit, whatever) will still be bottlenecked by the browser. If JS could send a single function call to mutate/morph a chunk of the DOM, and that was solved natively, we'd see massive efficiency wins. When you consider the massive scale of the web with billions of users, this surely will have an impact in the emissions of the electricity needed to run all that JS.
And (again) even if there were no perf improvements possible, you're avoiding the JS size argument. Lit still can be improved. Svelte generally produces smaller bundles than Lit. Eg see:
I'm not talking about one JS implementation vs another or if JS solutions are fast enough from the end user perspective.
The fastest JS solution (VDOM, Svelte, Lit, whatever) will still be bottlenecked by the browser. If JS could send a single function call to mutate/morph a chunk of the DOM, and that was solved natively, we'd see massive efficiency wins. When you consider the massive scale of the web with billions of users, this surely will have an impact in the emissions of the electricity needed to run all that JS.
And (again) even if there were no perf improvements possible, you're avoiding the JS size argument. Lit still can be improved. Svelte generally produces smaller bundles than Lit. Eg see:
https://krausest.github.io/js-framework-benchmark/current.ht...
But, again, if all the DOM mutation was solved natively there would be huge savings in the amount of JS shipped globally.