-
-
Replying to @patrickkettner @ken_wheeler and
Sheesh...Is this still the case on mobile for large DOM scenarios?
1 reply 0 retweets 0 likes -
Replying to @kaganasg @ken_wheeler and
@slightlylate would have a better view of the mobile landscape than I would1 reply 0 retweets 1 like -
Replying to @patrickkettner @kaganasg and
Scroll-linked effects are too hard; Houdini APIs coming to Chrome soon for this. Possible already, tho. GPU raster FTW. /cc
@RickByers1 reply 0 retweets 3 likes -
Replying to @slightlylate @patrickkettner and
Also, this participates in the app construction fallacy i see so many make. Native devs minimise view count. Webdevs should minimise nodes.
3 replies 1 retweet 8 likes -
Replying to @slightlylate @patrickkettner and
Obvious Q#1: Flipboard went to some trouble to do react-canvas from scratch. If it was as easy as DOM recycling, why reinvent the wheel?
1 reply 0 retweets 2 likes -
Replying to @kaganasg @patrickkettner and
Not a decision I would have made?
1 reply 0 retweets 0 likes -
Replying to @slightlylate @kaganasg and
But that was a time before pervasive GPU raster. Things change!
1 reply 0 retweets 0 likes -
Replying to @slightlylate @kaganasg and
GPU raster the way Chrome does it is not going to get us where we need.
2 replies 1 retweet 5 likes -
Replying to @pcwalton @slightlylate and
You refer to that Servo does it better, i.e. WebRender?
1 reply 0 retweets 1 like
I’d argue WR has a design that takes advantage of modern hardware better, yes. Not perfect, mind you :)
-
-
Replying to @pcwalton @nekrtemplar and
If you were so inclined, it would be really interesting to hear the differences between WR and blink rendering in more detail.
0 replies 0 retweets 3 likesThanks. 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.