> Inline loading of comments is the much better, smarter alternative.
with pagination, each page has a fixed number of comments, which means an expected amount of memory/CPU/network transfer. with inline loading, everything is loaded into the current page, which means the CPU and memory use essentially become unbounded, so the more you load the slower it goes.
> The last comments are loaded, you just gotta hit the page down key.
that's not how GitHub works. as I mentioned in the previous comment, this hidden comments are in the MIDDLE of the page, so page down doesn't make any sense here.
> The only thing that isn't loaded are the middle comments, and all you have to do there is tap load more comments link.
this only loads 60 comments, so in the example page I linked you'd need to:
1. click load more
2. scroll down until you find the end of the 60 new comments
and then repeat this process 7 more times. with pagination, the page links are always at the bottom, not randomly in the middle of the page, making for faster navigation.
> Yeah, a company that does over a billion API requests per day, they're not going to load 500 comments on a page
no one is asking them to do that. that's what the current system allows for. I am asking for pagination, which would split all the comments across pages, which would only be loaded on request.
You're wrong, sorry, it's very obvious to see using your browser tools that GitHub is in fact requesting those records when the link is clicked versus loading every comment:
load_more?after_cursor
Where do we see cursors? Typically in pagination. So it's obvious if you want to see everything and load everything, you can do so and it's devoid of javascript so you can ctrl-f all day.
> You get pagination in both API's, go write some code.
you seem to be making my own point for me. you're essentially saying, the website is so terrible, that users need to write their own frontend to make it usable. I agree!
No, I pointed out why you're wrong so you're moving the goalposts. You can get at all the data and instead of seeing the value in that, you rather complain about how terrible things are how stupid young people are. If anything, at this point I feel bad y'all are having problems clicking links.
> I feel bad y'all are having problems clicking links
They aren't even links. They are buttons that trigger JavaScript which makes a network request. That's quite different from an actual link that just loads some html
with pagination, each page has a fixed number of comments, which means an expected amount of memory/CPU/network transfer. with inline loading, everything is loaded into the current page, which means the CPU and memory use essentially become unbounded, so the more you load the slower it goes.
> The last comments are loaded, you just gotta hit the page down key.
that's not how GitHub works. as I mentioned in the previous comment, this hidden comments are in the MIDDLE of the page, so page down doesn't make any sense here.
> The only thing that isn't loaded are the middle comments, and all you have to do there is tap load more comments link.
this only loads 60 comments, so in the example page I linked you'd need to:
1. click load more
2. scroll down until you find the end of the 60 new comments
and then repeat this process 7 more times. with pagination, the page links are always at the bottom, not randomly in the middle of the page, making for faster navigation.
> Yeah, a company that does over a billion API requests per day, they're not going to load 500 comments on a page
no one is asking them to do that. that's what the current system allows for. I am asking for pagination, which would split all the comments across pages, which would only be loaded on request.