# The End of Pagination

**URL:** <https://discourse.codinghorror.com/t/the-end-of-pagination/64>\
**Category:** blog\
**Created:** [March 27, 2012, 12:00am UTC](https://discourse.codinghorror.com/t/the-end-of-pagination/64 "2012-03-27T00:00:00Z")\
**Posts on this page:** 1\
**Showing post:** 54

<div class="post-metadata">

**Author:** ![DavidE](https://discourse.codinghorror.com/letter_avatar_proxy/v2/letter/d/258eb7/32.png) [@DavidE](https://discourse.codinghorror.com/u/DavidE)\
**Post date:** [March 29, 2012, 12:00am UTC](https://discourse.codinghorror.com/t/the-end-of-pagination/64/54 "2012-03-29T00:00:00Z")

</div>

When I am on mobile net, especially if the connection isn’t all that great the infinite pagination can be frustrating on image searches and the like, especially if I want to load something else concurrently too.

In my opinion the best solution isn’t doing away with pagination, but rather it should be supported by the browser. If I could visit a new site and I would just have to hit a UI button or a hotkey instead of looking for the (usually small) page controls, that would be awesome. Another addition is, that if the scheme would be supported by the browser, than you could start preloading the content of the other pages (hopefully only the textual) once the current is finished so you could search those pages too with the browser’s search feature.  
I don’t know, this sounds really utopistic and I think it would require W3C implementing a new standard. Maybe in the next decade…

---

_[View the full topic](https://discourse.codinghorror.com/t/the-end-of-pagination/64)._
