3 ms·

EDIT: my comment is wrong because it confuses Data-Driven Design and Data-Oriented Design. Thanks @Narishma for the correction. DOD is pretty great, but I would

EDIT: my comment is wrong because it confuses Data-Driven Design and Data-Oriented Design. Thanks @Narishma for the correction. DOD is pretty great, but I wouldn't push for DDD outside game engines. --- I see DDD as a counter movement to OOP: expose your fields, don't bake behaviors into your data structures, and accept primitive types instead of instances of the internal class MyData. To me it doesn't imply "convert your code into data", which seems to be OPs only gripe with it.

Narishma 3y ago
What you're talking about is data-oriented design. Data-driven programming is something different. https://en.wikipedia.org/wiki/Data-oriented_design https://en.wikipedia.org/wiki/Data-oriented_design https://en.wikipedia.org/wiki/Data-driven_programming https://en.wikipedia.org/wiki/Data-driven_programming
- albedoa 3y ago
  I don't see how this comment section can recover from the confusion. Most of the comments are either confusing data-driven development (which is possibly bad) for data-oriented design (which is good) and wondering what the author's issue is with the latter; asking or helping to define what data-driven development is; griping that "DDD" is a reserved term; or some combination of those!
- deleted 3y ago
  [deleted]
- BoppreH 3y ago
  Oh no, you're absolutely right. I can't delete my rubbish post, but I've added a disclaimer, thank you very much. Also, it seems that DDD can mean Domain-Driven Design, so that's a confusing namespace to navigate. https://en.wikipedia.org/wiki/Domain-driven_design https://en.wikipedia.org/wiki/Domain-driven_design
deleted 3y ago
[deleted]