I really wish the conversion about web components was better framed.
Web components will NOT replace your framework.
They are awesome because they don't NEED to replace your framework to provide massive value to you.
-
-
just toggle the customElement compiler option in the REPL — all the WC stuff is purely additive. And then of course there's the fact that you have to put your CSS in JS ;) https://v3.svelte.technology/repl?version=3.0.0-beta.23&gist=3f2c0013217ad0a179ac01f0496208ff …pic.twitter.com/B5LbKgUdTh
-
(note that it will only compile as a customElement if you specify a tag name; easiest way to do so in the REPL is to add <svelte:options tag="hello-world"/> at the top of the file)
- 24 more replies
New conversation -
-
-
but as the stack of svelte components increases, will not repetitive code be generated? that could surpass that of a framework... only in the case that each component is added independently
-
In theory, yes, there's an inflection point. In practice, no — as long as you're using code-splitting, the components for any given page of your app are very unlikely to outweigh the typical framework. But in any case the beauty of a declarative authoring format is that we
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
to highlighting cases where web components allow folks to swap out a large fw for something lighter and more interoperable, but provocative headlines & context-free statements hurt more than help, IMO.