Most people have a wishy washy view between the differences between FP and OOP. It is never clear why a map reduce is
better than a for loop or vice versa.
That being said iS an area where OOP is definitively worse than FP: In fact OOP (as defined by JAVA and C++) is Categorically less modular than FP.
There is concrete and definitive reasoning behind why this is the case.
I've explained it all in a thread before I'll just link it for people who disagree or are curious.
> It is never clear why a map reduce is better than a for loop or vice versa.
to me map/reduce feel like a further development of structured programming. a map(...) call is less expressive / more constrained than a loop and that's the point; compare to how loops and if/else can all be written with goto, but we prefer the more structured alternative
That being said iS an area where OOP is definitively worse than FP: In fact OOP (as defined by JAVA and C++) is Categorically less modular than FP.
There is concrete and definitive reasoning behind why this is the case.
I've explained it all in a thread before I'll just link it for people who disagree or are curious.
https://news.ycombinator.com/item?id=19910450