I’m one of those people who has only used the page[number] page[size] implementation and that is or was a thing our frontend developers hated. What I mean by hated is the links object with first, last, and so on values, so instead we added headers also to include a count of all records, current page, next page and so on.
On thing to take note of is that the json specifications are open to most kinds of pagination
and if the implementation the team did (that i worked in) would have been done only with the json api specifications then we would probably had included a meta object in the links object like the discussion in Pagination controls.