This is not really accurate.
Let's compare in such way: Does FP give you as much overall capabilities as OOP? Put another way, can FP replace OOP? I think not. But the vise could be kinda correct.
This is not really accurate.
Let's compare in such way: Does FP give you as much overall capabilities as OOP? Put another way, can FP replace OOP? I think not. But the vise could be kinda correct.
This is an argument with no winner. I don't know how much experience you have with FP but the debate could go on and on. Anything you can do with OOP techniques you can do with FP and viceversa. It all depends on how much pain you want to endure (and that goes both ways).
That's the argument actually what I've been pushing. We agree that both have advantages/disadvantages, but for quantitative programming, object oriented programming can swallow FP capabilities (some of them painfully or not though), which doesn't mean FP cannot be more efficient in numerous cases. All can be done in both, but simplification directs to the OOP. Non object based programming languages generally are getting lost I think.