As per the title:

Why is TableListField's pagination disabled on a readonly transformation?

On a system I'm working on there may be many thousands of records on the many side of a one-many join, and if someone can't edit but can view the record on the one-side they are shown (or at least the system attempts to show them) a non-paginated list of these records, which is unmanageable at best and completely rubbish when the server crashes out during the generation of a list thousands of records long that we didn't want in the first place anyway.

Having traced this back in TableListField's history, this seems to be from before the open-sourcing of SS, so I was just wondering about the justification behind this.