OOP’s impact on data arrangement was a 35 year mistake

OOP’s impact on data arrangement was a 35 year mistake

Casey Muratori at the Better Software Conference walks us through how data in game development (and other systems) started with simple coherent structures and then morphed into hierarchies of objects, following the in-vogue trend of late 90’s programming.

This lead to changing the compile-time data arrangement from what’s best for the computer to compiling data to what is arbitrarily arranged to match the real-world things you’re trying to model.

He does a great job of breaking down the history and effects of what has happened in the 20 years since. Today, developers from racing games to AI are re-discovering that laying things out linearly and adhering to cache consistent access (ex: GPUs) is where the highest end performance is unleashed.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.