Also, the article does a really poor job of describing any drawbacks of Data Oriented Design. It's a real pet-peeve of mine. > Drawbacks of Data-Oriented Desig

Also, the article does a really poor job of describing any drawbacks of Data Oriented Design. It's a real pet-peeve of mine. > Drawbacks of Data-Oriented Design Data-oriented design is not the silver bullet to all the problems in game development. Ok, they don't view it as a silver bullet. This seems promising for an evenhanded discussion. I'm curious what the author thinks the drawbacks are. > The main problem with data-oriented design is that it’s different from what most programmers are used to or learned in school. So the first drawback is that nobody knows your silver-bullet? That's a cop out. > Also, because it’s a different approach, it can be challenging to interface with existing code, written in a more OOP or procedural way. And the second drawback is that code was written without using your silver-bullet? Seriously? If the only two things you believe are drawbacks about your tech are that not enough people know it, and not enough people are using it then it's not an even handed discussion of your tech. Discuss the actual trade-offs you've learned from using it. Not nonsense like nobody knows how wonderful it is, nor is using it. And that's coming from someone who agrees that OOP has huge flaws and with the most common applications of inheritance creates many flawed program architectures.