Although many firms have requested that we allow users to change the default number of items displayed per page, we've taken a different path to resolve this issue -- we're eliminating pagination on list views.
Rather than breaking large lists into pages, we're implementing what is known as endless scroll. When the page is first requested, we'll display a pre-defined number of items. While the user is reviewing the first set of items delivered, we'll fetch additional items. In the background, we'll be checking access and preparing the items for display. As the user scrolls down the page, we'll display the pre-fetched items, and fetch additional items in the background. With this functionality, the user doesn't need to wait for all items to be returned, checked for access, and displayed - we only get additional items when needed. If the user finds what they need on the first "page" in the endless scroll, the system hasn't wasted resources retrieving hundreds or thousands of items. Another benefit: no need to click Next and Previous.
This functionality has already been implemented in folders, and we'll be including it in all list views (workspaces, filters, saved searches, search results...). We'll be rolling this out in 17.2, but I can't guarantee that all list views will have the functionality by that date (if you quote me on 17.2, I'll deny it). I'd be interested in your feedback on this. Please contact me directly at firstname.lastname@example.org with your comments, complaints, suggestions or praise. :-)