I always find it funny to see calls to “unlearn oop”. It’s a tool, useful in some contexts and not useful in others. At some point industry treated it like a silver bullet, and now people are reacting to it by checks notes treating the hot new paradigm as a silver bullet.

learn oop, learn fp, learn logic programming, learn whatever you want. Also, learn when not to use them.

[–] expr@programming.dev 2 points 1 month ago (8 children)

FP has been around a long time, and yes, it is outright better than OOP. Sorry. I write Haskell professionally, and never have I ever felt like something would be easier done in an OOP language. Quite the opposite.

Unrestricted mutation makes programming really hard, and OOP and mutability go hand-in-hand. If you try to make immutable objects, then you're just doing FP with worse ergonomics.

[–] luciole@beehaw.org 39 points 1 month ago (2 children)

I would humbly suggest FP may seem especially natural to you precisely because that's what you use all day.

[–] expr@programming.dev 7 points 1 month ago (1 children)

I mean, I have an OOP background. I found FP as a result of my dissatisfaction with OOP. In fact, I used to teach OOP languages to new students and saw the same mistakes over and over again, mistakes that are simply not possible in FP. It's a very similar story for everyone I work with, too. We all had jobs in various OOP languages before we managed to get jobs writing Haskell.

Oh, and I'm currently teaching Haskell to someone at work who has a CS degree and has only done OOP languages (and C), and while it's different than what he's used to, he's still picking it up very quickly (working towards making him a junior engineer, which I think shouldn't take too much longer). In fact, just the other day we pair programmed on a bug ticket I have and he was not only following along with the code, he spotted issues I hadn't seen yet. Part of it is certainly that's he smart (which is why I'm doing this in the first place), but part of it is also that, with a bit of familiarity, FP languages are incredibly easy to read and follow. The primary difference is that FP does everything explicitly, whereas OOP encourages a lot of implicit (and hidden) behavior. When you organize code around functions, there's necessarily more explicit arguments and explicit return values, which makes it far, far easier to follow the flow of logic of code (and test!). Recently I was trying to read through our Kotlin codebase at work (for our Android app), and it was so much harder because so much is implicit.

[–] AbeilleVegane@beehaw.org 2 points 1 month ago

Please Grok tell me why was I so invested in this discussion, even if I'm not quite sure what OOP is?

load more comments (5 replies)

load more comments (9 replies)