4 ms·
I found an article which has similar rules: * Use FP when you need to build something purely computational. * Use OOP when you want/need to build something ge
by gardaani 8y ago
I found an article which has similar rules:
* Use FP when you need to build something purely computational.
* Use OOP when you want/need to build something generic for other people to use.
* But if you are application or game developer, ECS way of thinking brings a lot of benefit to the table.
https://hackernoon.com/when-not-to-use-ecs-48362c71cf47 https://hackernoon.com/when-not-to-use-ecs-48362c71cf47
- yogthos 8y agoI have to disagree here. It's much easier to use data driven APIs than OO ones. With the former you get what you see and there are no additional rules. You call the API, it produces some result that you can use in any way you like. Meanwhile, objects have behaviors and internal state that you have to understand because each object is its own ad hoc DSL with its own rules and behaviors.