So HN should be a single page with all submissions ever? ;)
Yes, don't unnecessarily break up content. But most pages are going to include lists of some sort that you want to be paginated in some way.
If you look at HNs /new queue, there are submission IDs in the next links, so you can click "more" multiple times without seeing content multiple times, even if new submissions have pushed them down in the global list by now. Useful if there are many updates and new entries come in at the "top" of the list.
So if someone requires the entire table you think a single API call should just send it? Does it not occur to you that people used page data to limit response sizes and manage the performance of their API's?
detaro|10 years ago
Yes, don't unnecessarily break up content. But most pages are going to include lists of some sort that you want to be paginated in some way.
If you look at HNs /new queue, there are submission IDs in the next links, so you can click "more" multiple times without seeing content multiple times, even if new submissions have pushed them down in the global list by now. Useful if there are many updates and new entries come in at the "top" of the list.
gnaritas|10 years ago