timwis
commented
7 years ago Clusterize.js is great but expects dom strings. But maybe that's okay -- our events are now bound to the parent tbody, so the trs are pretty basic and could be rendered as strings, particularly if we cache them so only Clusterize can update them.
Currently, anything over 50 table rows starts to get a bit laggy with keyboard events. Ideally, the UI would only render (and bind events to) rows within view. It's probably safe to put the whole table into memory and just say this app isn't ideal for massive tables; otherwise we'd also have to support infinite-scroll-style fetching.
Related: editdata/infinite-elements