When I helped start the Web Components effort, a goal was to end framework wars at the component level. About time:https://twitter.com/domenic/status/769344873027829760 …
-
-
I think there's a path forward, but WC proponents should try to help improve areas FWs are concerned about.
-
one major difference: promises were adopted by FWs quickly. WC proponents highly correlated with Chrome/Polymer.
-
that's a good point. Might be because of polyfillability, but maybe not. I do find this very worrying.
-
I think part of it is that polymer folks rely a lot on non-standard extensions and say "Things look great from here!"
-
I brought up theming years ago and the situation is still pretty meh (at best) for standard WCs.
-
custom properties, calc, variables, etc certainly help but we need a full solution for theming worked out.
-
and I'm really glad we're moving to leaf nodes and away from <my-ajax> and <my-app> which just don't work.
-
another concern: WCs do a lot of standalone, non-coordinated work. At a client, I saw WCs that were making XHRs 1/
- 4 more replies
New conversation -
-
-
so: generic 'children' API. But other than that, it's all black-box, right?
-
heh I didn't mean API. I meant the process of iterating on the feature as an outsider.
-
right right right. Endemic problems of means of standardisation & political abuse thereof.
-
not necessarily. I think TC39 works better (not perfect, but better)
-
yes, you would... :-/
-
Promises went fast. The proof is in the pudding. TC39 is emotionally intense but things get into all browsers faster.
-
Huh let's be fair; Promises are incomparably small compared to web components.
-
changing the way async programming works on the platform wasn't a small thing :)
- 2 more replies
New conversation -
-
-
yeah agreed leaf nodes are where it's at.
-
agree, but leaf nodes turn out to be a small amount of the complexity in an app, so WCs have modest impact.
-
-
yes, but if WC are for leaves, you still need a FW compnent system too, because many components aren't leaves
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.