3 ms·
As a rule, FP is great for separating concerns in independent code. So you can have a great data-access layer, and a completely abstract data layer that doesn't
by marcosdumay 7y ago
As a rule, FP is great for separating concerns in independent code. So you can have a great data-access layer, and a completely abstract data layer that doesn't care about the access layer at all. OOP systems nominally do that separation too, but FP usually makes those layers clearer and more independent.
A reduction in total complexity is another, completely unrelated thing. I honestly do not see accidental complexity on your description. Any system will have to deal with all that stuff, OOP and FP will just do it in different parts of the code.