Some code snippets and images would really help here. Also some more concrete examples.<p>I understand the main point that data is everything, but the author's arguments are hard to learn and go over my head.
For anyone interested into very light forays of DoD in C++, I've put out this library recently which allows to have an "object" API on top of an array-based storage (AoS interface / SoA implementation): <a href="https://github.com/celtera/ahsohtoa" rel="nofollow">https://github.com/celtera/ahsohtoa</a>
To be honest i wish there was some sort of situational Design Paradigm - the VIM of languages. OO in the design of the Structures/Debug-Data Representation, DOD in the structures and algos, functional whenever the programmer itself is represented (the "marshallers and handlers" in OO.)<p>Somewhere in this triangle of worlds, there is a optimum of speed, debug and reason ability and beautiful code with minimal repetition..
Specificity and examples are critical and the article lacks both. It's somewhat ironic that the author talks about the importance of data yet offers few examples and datapoints of where this paradigm works and doesn't work.<p>Without specificity, the merits of the design are not falsifiable.