That’s not what I had in mind when creating SimplePagination. The implementation of the core served the purpose to keep existing paginations intact (extension manager, backend user module). The implementation is marked final for a reason. The interface is the important piece of code here. It guarantees how your paginator behaves. Hence, it was intentional to keep SimplePagination simple and let people implement their own implementations if needed. All that means, that we should rather talk about the interface instead of the implementation.
That’s what I had in mind back then. But those don’t need to be extensions, it can be simple composer packages.
Furthermore I second what Claus already said. I think the important part is the integrators’ experiences. That can definitely be improved but instead of giving the integrator all freedom like with the widget in the past, we should rather think about standards. It would be good to hear what integrators actually need besides a guarantee that an extension provides certain pagination data to be present.
As Claus said: Don’t. It contradicts the idea of the interface. Rather focus on that.
Could be a compromise although I personally don’t think that a specific implementation is important, rather the interface (again).