: so the right question is "can we get this at 60fps, under budget, easily?". Polymer shows "yes". Seems good to me.
-
-
Replying to @slightlylate @b_sted
requiring a dependency on a 3rd party library is myopic. Always reasons to reject it. Needs to be native to browsers
2 replies 0 retweets 0 likes -
then each library can innovate on top. And to clarify, Polymer showed a blank screen. Not 60fps scrolling....
2 replies 0 retweets 0 likes -
-
Replying to @slightlylate @b_sted
I clicked the link you shared in Twitter. Opened in app browser. Iphone 5SE
2 replies 0 retweets 0 likes -
Replying to @slightlylate
crashes for me in iOS chrome too :(
@chofter@b_stedpic.twitter.com/OtNIzfR0iW
3 replies 0 retweets 0 likes -
why not have Chrome lead the way with a native solution? Others will follow, as with so much you've done
1 reply 0 retweets 0 likes -
: we need a data source element first; next on my list once other browsers get one to web components v1
1 reply 0 retweets 0 likes -
Replying to @slightlylate
In a moment of serendipity, an entire blog post that expands on my "Web is Too Hard" meme https://hueniverse.com/2016/06/08/the-fucking-open-web/ …
1 reply 0 retweets 0 likes
: having learned more about @eranhammer's problems and stack, I'm not sure it's that clear-cut
/cc @dalmaer
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.