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.
3 replies 0 retweets 4 likes -
Replying to @wycats @slightlylate
that's a good point. Might be because of polyfillability, but maybe not. I do find this very worrying.
2 replies 0 retweets 3 likes -
Replying to @domenic @slightlylate
I think part of it is that polymer folks rely a lot on non-standard extensions and say "Things look great from here!"
1 reply 0 retweets 7 likes -
I brought up theming years ago and the situation is still pretty meh (at best) for standard WCs.
1 reply 0 retweets 1 like -
custom properties, calc, variables, etc certainly help but we need a full solution for theming worked out.
2 replies 0 retweets 3 likes -
and I'm really glad we're moving to leaf nodes and away from <my-ajax> and <my-app> which just don't work.
2 replies 0 retweets 7 likes -
another concern: WCs do a lot of standalone, non-coordinated work. At a client, I saw WCs that were making XHRs 1/
2 replies 0 retweets 3 likes -
and sleep(250) *per component*. Possible to coordinate, but hard when isolation is the value prop. 2/2
1 reply 0 retweets 2 likes -
TLDR I don't think anyone is "against" the tech per se; we are tired of being bludgeoned despite very real concerns.
1 reply 1 retweet 12 likes
there are some parallels with promises, but promises were a 1-year process with a ton of discussion from FWs and devs
-
-
let's get on that train and I bet the results will be good :-D
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.