Understand the core architectural difference between FlatList's VirtualizedList and FlashList's recycling approach.
FlatList (built on VirtualizedList) and FlashList both avoid rendering an entire dataset, but they differ fundamentally in how they manage off-screen rows. What is the key architectural difference that lets FlashList reduce jank and memory churn on large lists?