For points 1, 2, and 4, I do agree that solutions exist, but I found myself agreeing with the author that they're an issue simply because I run across enough si

For points 1, 2, and 4, I do agree that solutions exist, but I found myself agreeing with the author that they're an issue simply because I run across enough sites that continue to have these problems despite many good sites demonstrating how the pages should operate. I think the article's point would stick a little better though if the author focused more on the implementation than on the ∞scroll itself, since it's inconsistency across user experiences that causes frustration with ∞scroll, not so much ∞scroll itself. The only reliable constant across implementations of ∞scroll is that you'll be able to continually scroll; how it interacts with static content on the page, how it interacts with the back-button, and so on depends completely on how well it's implemented. It is very frustrating to come across sites where you follow a link far down in the page and hit back, only to be taken to the very top of the list and having to scroll and reload everything again. It's not even so much a performance issue; my old iPhone4s handles most ∞scroll just fine, but it's still just frustrating to go through pages and pages of scrolling because hitting Back didn't return me to where I was. This is particularly bad on mobile where fat-fingering links is pretty easy/common. Edit: not sure why you're getting down voted - I think your comments are fine and worth discussion; I also think they're wrong, but that's the point of discussion...