undefined | Better HN

0 pointscrimsonalucard6y ago0 comments

This isn't about OOP vs. FP.

This is about OOP vs. everything else.

Rust, Go and javascript are three languages that are moving away from the OOP paradigm. None of those three languages are classified as functional.

>Is there some resource you can point to that says in the past when faced with situation X developers tended to use pattern Y, these days that has been superseded with way of doing things Z?

No. A general trend is an anecdotal observation. Still a quick google search yielded: https://blog.cleancoder.com/uncle-bob/images/fpvsoo.jpg

Take a look at the following video:

https://www.youtube.com/watch?v=QM1iUe6IofM

While I don't agree with a lot of it, I think it sums up my opinion really clearly. It's not about DP's but because DP's focus around OOP and the video is a criticism of OOP therefore the arguments apply to DPs.

0 comments

3 comments · 1 top-level

james_s_tayler6y ago· 2 in thread

Thanks. I've observed this as a general trend too. I'm starting to become more and more interested in the functional way of thinking.

The image you linked it interesting. I want to dive more in on the how/specifics. I don't necessarily buy the argument it's trying to make that "just make a function and you no longer have a need for factory pattern". You're trying to accomplish something fairly specific with that. Functions compose, I could see how there are properties they have that can be leveraged to achieve the same goal, but I'm guessing the functions you write or the way you write functions to achieve each of those specific aims likely differ in subtle yet important ways. I'm very interested in those details.

crimsonalucardOP6y ago

>I don't necessarily buy the argument it's trying to make that "just make a function and you no longer have a need for factory pattern".

The same pattern is achievable with functions but the implementation is so trivial in FP that it doesn't even need a name:

Just have a function return another function. That's a function factory.

Same thing with dependency injection:

Just have a function take another function as a parameter.

Outside of this I wouldn't even recommend either pattern at all. It's bad practice in all paradigms. Only have data flow through your execution path, don't have new "execution paths" flowing through your execution paths, such architectures tend to be over-engineered.

james_s_tayler6y ago

Do you have a good example of a reference architecture or implementation of a non-trivial system you can point me to?

I've recently gotten a copy of the book Domain Modelling Made Functional. I'm yet to read it, but I'm pretty intrigued by some of what I've seen and I have heard it comes highly recommend.

I'd be very keen to hear of other high quality examples of things people consider good reference material.

1 more reply

j / k navigate · click thread line to collapse