3 ms·
You're right in that nothing about this is specific to OO or FP. However, under this model, you really don't want your actions in the actions list to change af
by yen223 9y ago
You're right in that nothing about this is specific to OO or FP.
However, under this model, you really don't want your actions in the actions list to change after the fact. That means those actions in the list really shouldn't be modeled as "objects" with object-like mutable internal state and all. In fact, you'd probably need them to be as lightweight as possible, which means no sticking methods on them.
With those constraints in mind, OO-style code brings nothing to the table.
- maxxxxx 9y agoI think this unfortunately goes into the same direction a lot of political discussions tend to go. Two rigid philosophies and one has to win. In the real world either one can work if applied correctly. And both can learn from each other. FP brings a lot of interesting concepts to the table that are useful. But I doubt that people that screw up OOP will screw up less with FP In the end competent and disciplined (in my view the number one attribute of a good dev) people will produce good software with any paradigm. Clueless people will cause problems no matter what the tool is.