If you're worrying about infinite scrolling, don't; we'd never.
So you are adding endless-scroll? One of the Web UI things that the HN community regularly complain about on other sites?
Please make it optional. :)
Not necessarily. I seem to remember that HN used to be without pagination, all the comments were just listed on one page (without any JS to load more comments etc) but servers started to struggle when HN got more users which led to sometimes too many comments, so they added the pagination.
Somehow I associate this with the thread when Steve Jobs died, but not sure how accurate that is. My memory is kind of sucky.
See also: isomorphic, real-time, serverless and countless others examples of poorly named concepts in web development.
Please don't. Or just make it optional. Infinite scrolling is evil.
Modern caching strategies mean it wouldn't be any database load or concerning computational overhead? I'm no expert on HN-scale sites though.
Anyway, my 2 cents is I'd prefer everything loaded at once, no pagination, no infinite scroll.
Why? Pagination seems like a good idea for really long threads.
Additionally, request count matters more than data transferred. It's much easier to serve 1MB to each of 100 users than 1KB to each of 100K users. n people are already going to view the comment thread for a submission - a several-dozen-KB increase in the amount of data that you send each of them (assuming you're serving them statically) results in anywhere from "little" to "imperceptibly" additional CPU load.
I'm assuming that what he means is that they'll replace the need to click on a link with the 'infinite scrolling' that you see on Fb, etc.