> You cannot build a 60fps scrolling list view with DOM.
I simply do not believe that. I have no problems scrolling around the internet. And the examples they give (flipboard.com/@flipboard) give me no clue about what their problem with the DOM is. I find it really hard to imagine you couldn't do that in the DOM.
I wonder what is going on over there.
Can't complain; their results do look gorgeous.
Flipboard spent an enormous amount of effort making a rendering to canvas platform, humorously to allow an "open" option aside from their app (which makes the complaint about it in the submission rather perplexing). I suspect they did a lot of analysis. And the DOM is notoriously slow, one of the reasons being that it is now a catch all/everything and the sink platform that has an enormous number of modifiers -- the flexibility that we hail is also what leads to engine slowdown. We need a new, simpler layout standard that simplifies all of the various sidepaths and diversions that got built into the standard.
I heard the same "argument" when Facebook went from HTML to native. Personally, I never attribute to expertise what adequately can be explained by stupidity.
http://techcrunch.com/2012/12/13/facebook-android-faster/
After Facebook went native, LinkedIn did some "why we went with HTML5" thing...and then not long after they went native.
You mentioned in another comment that you need to see a list that has troubles on your Nexus 4. I find it difficult to believe you use the web much on the device with such a claim -- I regularly use a Nexus 4, 5, 7 (2013), and I regularly encounter horrendous websites where the site is so grotesquely overloaded that scroll requests are acted on literally a second+ later.
I love the web. I endlessly evangelize the web. But it has serious, profound problems that its biggest champions had to completely work around or avoid altogether.
I said "minimal example". As Linus Torvalds puts it: Words are cheap, show me code.