An Introduction to Data Oriented Design with Rust
I&#x27;ve read quite a few articles about DOD. I get how DOD is great but there are reasons OOP is still around (surely?)<p>I suppose I&#x27;m still hung up on, what are the benefits of OOP that I&#x27;m missing?<p>It seems like there are reasons OOP is so ingrained. I can see a couple of reasons that are environmental. For instance, OOP is taught in schools because students are often taught to program before they&#x27;re taught about computer architecture - thus DOD would be lost on them. It would be a huge barrier to entry to introduce cache hit rates as a design concern when people are just learning what a class is (in the current standard model of CS education).<p>Still, it feels like there are other practical reasons to keep OOP around. Perhaps OOP is the React Native of design patterns - poor performance but quicker to write and add new members to. It does seem like there are also legitimate concerns about refactorability and extensibility of DOD code. Anyone have any more refined ideas here?