The era of interoperable web components is nearly here; the nightmare of siloed legacy frameworks like React, Ember and Angular nearly over!
-
-
@wycats Polymer has an explicit goal to be interoperable, and it adds to WCs to help implement WCs, but goal is to be just WCs on outside -
@wycats times where this doesn't hold up is usually a technical failing, ex: ShadyDOM and the CSS @ apply "polyfill", but goal is standards -
@wycats ie, these points where interop isn't seamless are unfortunate tradeoffs that are designed to be reversed when native feature arrives -
@wycats the existing Polymer "goo" on top of WCs is mostly templating and data observation, and will be very small when everything is native -
@wycats My initial tweet was definitely too snarky and conflated my "nightmare" of non-interop with the names of example frameworks -
@wycats however it's confusing to be accused of lip service and being bad actors, when we bend over backwards to interop and use standards -
@wycats afaict, we're one of the few to not just give lip service to interop, and to actually code towards it, even when it's not expedient
End of conversation
New conversation -
-
-
@wycats@justinfagnani as much as that is true, either trendy or luck seems to "win", IMOpic.twitter.com/E8FsmGtufa
-
@printf@justinfagnani you perceive Polymer to be winning? -
-
@justinfagnani@printf I don't care about "winning", but disagree about the exact points of high-level interop. Seen some WC nightmares.
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.

