The iPhone table programming guide says to carefully consider the "tradeoff between optimal scrolling performance and optimal editing performance."
What type of "editing" would result in bad performance if cell contentViews are custom drawn via drawRect:?
I can imagine the animations in a row drag and drop not working well. But what about the simple row selection edit where the cells just slide to the right 30 pixels and reveal delete icons on the left? Could that really be more taxing than scrolling?
I have read a million posts on scroll performance and I really prefer using drawRect: in a custom UIView, (I would need 5 or 6 subviews to use the subview method of configuring a cell.) but Apple has me spooked.