the use case of doing the pagination 100% on the client apply only for when you know you dataset is small, <2000 records. You don't want you table to render in the DOM 2000 rows then you paginate in the client for performance reasons(less DOM elements)
Fetching that amount of data(<2000) is not a problem today in my opinion. If the use case is other(> 2000 records) then server side pagination :)
Valid to say the 2000 records is a number made my me :) ... it could be more or less
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
the use case of doing the pagination 100% on the client apply only for when you know you dataset is small, <2000 records. You don't want you table to render in the DOM 2000 rows then you paginate in the client for performance reasons(less DOM elements)
Fetching that amount of data(<2000) is not a problem today in my opinion. If the use case is other(> 2000 records) then server side pagination :)
Valid to say the 2000 records is a number made my me :) ... it could be more or less