broken for me too. This is my point. Its too hard. Needs to be native not a library
-
-
I've built at least 3 versions of this. Alex I even showed you a great one running 60fps 4 years ago. Too hard
1 reply 0 retweets 2 likes -
and that was with images and variable height rows. Devs should NOT have to build this over and over. Mobile == Lists
1 reply 0 retweets 0 likes -
Replying to @chofter
: even if I agree with you here, I have zero faith in browsers to do a good job of it in a timely way; hence primitives
1 reply 0 retweets 1 like -
Replying to @slightlylate @chofter
: so the right question is "can we get this at 60fps, under budget, easily?". Polymer shows "yes". Seems good to me.
1 reply 0 retweets 0 likes -
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 -
pro in in that even for awesome debs on Polymer its too hard. Lack of native solution is holding the web back
1 reply 0 retweets 0 likes -
Replying to @chofter
: polymer is (almost) as easy as it can get. You need a data source and a sink. This makes that markup
1 reply 0 retweets 0 likes -
Replying to @slightlylate @b_sted
well sell React with the same marketing. We all rebuild variations on components(Dojo widgets in 2004?). Too hard.
1 reply 0 retweets 1 like
: i see the crash.
/cc @TaylorTheSavage
-
-
: likely iOS/safari bug. *sigh*
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.