Pitfalls of Object Oriented Programming (2009) [pdf]

Context! Context! Context!<p>This is about game programming, and how to optimize your data to be cache- and prefetch-friendly.<p>If your data doesn&#x27;t look like game data, or isn&#x27;t accessed like game data, it won&#x27;t help and the &quot;pitfalls&quot; aren&#x27;t.

I&#x27;ve really enjoyed reading <a href="http://bitsquid.blogspot.com/" rel="nofollow">http:&#x2F;&#x2F;bitsquid.blogspot.com&#x2F;</a> . It runs right from the birth of their game engine right up to the recent acquisition by Autodesk. They are heavy proponents of data-centric design with flat layouts (no pointer graphs jumping all over memory). The result is a game engine where almost anything (from rendering pipelines to physics models to ai) can be changed, compiled and live-updated on a nearby console in under a second.<p>EDIT: <a href="http://bitsquid.blogspot.com/2011/12/pragmatic-approach-to-performance.html" rel="nofollow">http:&#x2F;&#x2F;bitsquid.blogspot.com&#x2F;2011&#x2F;12&#x2F;pragmatic-approach-to-p...</a> is a particularly good overview

Related: <a href="http://www.dataorienteddesign.com/dodmain/dodmain.html" rel="nofollow">http:&#x2F;&#x2F;www.dataorienteddesign.com&#x2F;dodmain&#x2F;dodmain.html</a>

We might also think of this as modern architectures being very badly suited for supporting these mechanisms for abstraction. This may indicate an opportunity.

I wouldn&#x27;t say these are pitfalls of OO. They are merely antipatterns in OO game programming (I might add, with any high-throughput data programming).