3 ms·
I think that this isn't a symptom of OO vs FP, but rather of the types of designs that arise from OO and FP systems. In my mind, it boils down to composability
by JamesSwift 12y ago
I think that this isn't a symptom of OO vs FP, but rather of the types of designs that arise from OO and FP systems. In my mind, it boils down to composability and orthogonality. The quote that comes to mind is:
"It is better to have 100 functions operate on one data structure than to have 10 functions operate on 10 data structures."
I think OO tends to go with the 10 functions on 10 data structures, whereas the FP goes with 100 on 1. Once you are able to abstract your API in such a way, the work of creating these 'multiple levels of abstractions' becomes an exercise for the reader, because of the composability of the API.