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 …
-
-
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/
-
and sleep(250) *per component*. Possible to coordinate, but hard when isolation is the value prop. 2/2
- 3 more replies
New conversation -
-
-
it's a little hard when frameworks have moved away from the platform (E, A, R all use nonstandard HTML parsers)
-
the only non-standard extension I can think of in Ember is /> which I'd drop for a good reason.
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.