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 …
-
-
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
-
TLDR I don't think anyone is "against" the tech per se; we are tired of being bludgeoned despite very real concerns.
- 2 more replies
New conversation -
-
-
I think there's a path forward here, but it really has to involve coming to understand the concerns.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I take exception to the notion that Web Components == Polymer's style and use of them, it's just not true.
-
I just did a whole writeup this week because I got sick of the FUD: http://www.backalleycoder.com/2016/08/26/demythstifying-web-components/ …
- 7 more replies
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.