@justinfagnani example: Shadow DOM should not be coupled to event retargeting. I could barely get that concern a hearing.
-
-
Replying to @wycats
@justinfagnani I've taken days off of work to try and collaborate, but the WC train is on full speed and can't be redirected
1 reply 0 retweets 0 likes -
Replying to @wycats
@justinfagnani It's also dismissive of the work of React/Angular/Ember to call us "legacy" without trying to grok why we're not "just WC"2 replies 0 retweets 2 likes -
Replying to @wycats
@justinfagnani Polymer builds just as much a layer of goop on top of the deficiencies of WC as Ember/Angular/React but you didn't mention it2 replies 0 retweets 2 likes -
Replying to @justinfagnani
@wycats times where this doesn't hold up is usually a technical failing, ex: ShadyDOM and the CSS @ apply "polyfill", but goal is standards2 replies 0 retweets 0 likes -
Replying to @justinfagnani
@wycats ie, these points where interop isn't seamless are unfortunate tradeoffs that are designed to be reversed when native feature arrives1 reply 0 retweets 0 likes -
Replying to @justinfagnani
@wycats the existing Polymer "goo" on top of WCs is mostly templating and data observation, and will be very small when everything is native2 replies 0 retweets 0 likes -
Replying to @justinfagnani
@wycats My initial tweet was definitely too snarky and conflated my "nightmare" of non-interop with the names of example frameworks2 replies 0 retweets 1 like -
Replying to @justinfagnani
@wycats however it's confusing to be accused of lip service and being bad actors, when we bend over backwards to interop and use standards2 replies 0 retweets 0 likes
@justinfagnani I'm sorry if something I said sounded like either of these. I just don't feel like Polymer is all that different.
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.