Fair criticisms of #webcomponents by @sebmarkbage at #reacteurope...better portability is lower level APIs to bypass HTML/CSS/box completely
-
-
Replying to @AndrewRota
I worry about what we lose by rejecting DOM altogether. Of course we gain a lot, but is it worth the trade off?
@sebmarkbage#reacteurope2 replies 0 retweets 3 likes -
Replying to @AndrewRota
@AndrewRota That's a totally valid concern. It is something we will have to play with and evaluate. Worth experimenting. :)2 replies 0 retweets 2 likes -
Replying to @sebmarkbage
@sebmarkbage@AndrewRota FYI Angular 2 wants exploit power of web components but reality for right now is perf is not there.1 reply 0 retweets 0 likes -
Replying to @jeffwhelpley
@sebmarkbage@AndrewRota which is why ng2 components act like web components and can integrate to web components but are not web components1 reply 0 retweets 0 likes -
Replying to @jeffwhelpley
@jeffwhelpley@sebmarkbage Yeah there are still some significant problems w/#webcomponents, though they're mostly the same problems w/ DOM.1 reply 0 retweets 0 likes -
Replying to @AndrewRota
@jeffwhelpley@sebmarkbage Is the solution to spend time building on DOM paradigm (#webcomponents) or instead try bypassing DOM altogether?1 reply 0 retweets 1 like
@AndrewRota @jeffwhelpley @sebmarkbage : none of what was posted in this thread makes sense from a runtime/browser perspective, FYI.
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.