Re:Facebook explains what's wrong with the mobile web
by comex on Sunday September 16, 2012 @01:03AM
(#4528300)
After vast amounts of effort spent on fancy JITs and fast layout engines, browsers should be able to do this stuff - or at the very least, it would be cool if they could, and it's probably achievable. Editorialized submission title aside, this post is the starting point for an attempt to improve browsers in the future, and in the meantime Facebook has launched their native app to provide the desired experience a different way. Where exactly is the whining?
Re:Facebook explains what's wrong with the mobile web
by akira2501 on Sunday September 16, 2012 @02:21AM
(#4528459)
Why should the browser be required to deal with this? They used javascript to build up a giant page, why don't they use the same facilities to cull the parts of the page that have already scrolled off the top of the screen?
Everyone wants rich apps in the browser, but no one wants to pay the price of it.
Re:Facebook explains what's wrong with the mobile web
by comex on Sunday September 16, 2012 @02:36AM
(#4528489)
Read all the issues listed in the post - it's not just about removing stuff, there are a whole bunch of obstacles to pages trying to take control of scrolling in general or even modifying the DOM without causing stuttering.
The phone manufacturers aren't deliberately making infinite scroll perform poorly just to piss off Facebook. The devices, at this time, are not powerful enough to support infinite scroll when using HTML and Javascript. FB could get over it and use something else, but they've decided to whine about it instead.
Also, "native apps can do it, therefore HTML should be able to do it" is almost hilarious. Native apps are faster than HTML/Javascript. That's not news - that's the way it's always been and probably always will be. Everybody else adjusts their designs to deal with it; Facebook is just whining about it.