Popular posts

None or Both it depends on your mindset and what you've learned.

I think both of them complement each others but I'm not a purist. I am a pragmatist in the end.

So concurrency I want to solve functional. Communication between components I want to solve in a OOP manor.

One important thing is that you have to consider that functional programming is supported as soon as you have

• functions "first class citizen" -> which means you can assign them as variables and/or pass them as a parameter
• immutable data structures

Which most modern OOP languages support. So you can code functional in OOP but you cannot code OOP in functional languages.

Both try to solve the "global mutable state" issue

• OOP by controlling "messaging" -> controll which parts can mutate the state (primarly working on the heap-memory-segment)
• Function by removing mutations -> functional programming copies / vector changes the data and passes it to the next function (primarly working on the stack-memory-segment)

So I personally don't think any of the paradigms is easier to learn, and tbh I think basic functional programming is more approachable because "add(x, y)" is easier to understand than "class calc { public add(x, y) }" since now you have to understand what is a class, what are access rights and so on.

but it boils down to taste in the end I guess ....