Crap. I think I'm not going to use webcomponents at all; they cannot be rendered on the server -> they don't solve today's problems
-
@alexindigo server has no concept of DOM, whereas webcomponent fully rely on it. Workarounds are either clunky, fragile and slow
@alexindigo it's better to flip it around: create a component using minimal glue (e.g. I like virtual-hyperscript) and then -> webcomponent
-
-
@alexindigo though I'm failing to see any usecase for webcomponents at this point; initial render matters and they're not good for that -
@yoshuawuyts This is my problem with WC — sync-looking API, either blocking or a hack. HTTP2 could partially solve it all though.
End of conversation
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.