@yiningkarlli@mastodon.gamedev.place
2026-07-26 19:47 UTC
I’m confused by all of the people who are like “data oriented design means use struct of arrays and use so-and-so patterns”. I thought the whole point of DoD was to understand your data transformations first and tailor your solution accordingly, not just blindly apply patterns. If a SoA layout doesn’t actually match your data access pattern, then just blindly applying SoA is not DoD; it’s actually the opposite of it!
Replies (2)
-
@yiningkarlli@mastodon.gamedev.place 2026-07-26 20:08
It’s like a lot of people that watched the Mike Acton CppCon talk totally ignored the first half where he was like “the solution is to not be prescriptive with patterns” and only payed attention to the example in the second half and took that as a prescriptive pattern.
-
@jkaniarz@mastodon.gamedev.place 2026-07-26 21:06
@yiningkarlli@mastodon.gamedev.place The first guide to DoD I read spelled this out. It even gave an example where Vector3s were split into an array of XY and an array of Z because it fit the code’s access pattern better.