> How would you implement a deep pagination like "go to page 107" You wouldn't. Keyset pagination forces the user to do the exact same thing people complain ab

> How would you implement a deep pagination like "go to page 107" You wouldn't. Keyset pagination forces the user to do the exact same thing people complain about you doing to the database. Want page 10 of results? Too bad, enjoy running through pages 1-9 and throwing them away. Except now everything is even slower because it's users talking to the service, not the service talking to the db. There are plenty of use cases where that's a perfectly acceptable trade-off, or an annoying-but-necessary trade-off, but the people all up in a froth over the inefficiency of limit/offset seem to regularly fail to realize that they're advocating for a database performance solution with implications that reach all the way out to the UI/UX level. At a minimum, I see very little in the way of acknowledgement of this factor.