@abuukar I think which is best depends on the situation.

Jeffrey covers the pros/cons of cursorPaginate at around 08:55 in the video. My thinking based on that is: If I were creating an app where short urls and SEO doesn't matter or where the app uses infinite scroll and there are a lot of records, I would consider cursorPaginate as a more performant option.

Now whether to use paginate or simplePaginate comes down to user preference. Depending on what the app is for, I might have users who need to be able to quickly navigate directly to specific pages without having to click the prev or next button multiple times to get to it.

I'm thinking of the inventory system at my current job where a user might be looking through records, get to page 10 and need to compare with something they thought they saw on page 2 and 5. Now they could change the page number in the url or click the prev/next buttons multiple times or if individual page buttons were available it would be really convenient to just click once on 2, 5, 10 to jump around. So in this case I would go with paginate.

For something like a forum look at the Laracasts forum. I think most users make more use of the filters and search box or find the right page through a google search. I don't think many users specifically want to click to go to page 2. So simplePaginate is a good choice for this kind of thing. I honestly did not know until now that there were buttons down there because I've never seen that part of the page.

All You Need to Know About Pagination

Updated Series Available