I had a major hand in writing the CPTableView class in Cappuccino. The tableview is designed to handle hundreds of thousands of rows without slowing down. This

I had a major hand in writing the CPTableView class in Cappuccino. The tableview is designed to handle hundreds of thousands of rows without slowing down. This is accomplished both through very aggressive caching, and the smart use of algorithms. If you look at the source code, you can actually see where we document the time complexity. A standard tableview (static row heights) is laid out in constant time, whereas using variable row heights is laid out in logarithmic time. An early implementation provided variable row heights in linear time (or perhaps n^2, I don't recall)... this caused scrolling to be absolutely terrible and unusable if you had more than a couple dozen rows. With constant time we can, theoretically, have any number of rows in your tableview and it will remain just as performant as if you only had 1. If you're building real software and throw out the concept of time complexity, then you're setting yourself up for failure in the long run.