This means that you can do things like send messages to objects written in different languages, transmit object definitions by mail, send messages via SMS, etc. In my opinion this is where a lot of the power of βmessage-passingβ lies, but itβs also one of the least explored aspects.
I would agree that it's a messy topic. OOP gets a bad wrap for easily producing messy code. In my experience, using messaging patterns and isolating code properly can avoid this.
There is such a thing as messy and hard-to-understand FP code too π
There is messy OOP code too.
There is well-structured FP. And well-structured OOP.
I enjoyed your article for pointing this out π
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I like that first article you linked π
This stuck out to me:
I would agree that it's a messy topic. OOP gets a bad wrap for easily producing messy code. In my experience, using messaging patterns and isolating code properly can avoid this.
There is such a thing as messy and hard-to-understand FP code too π
There is messy OOP code too.
There is well-structured FP. And well-structured OOP.
I enjoyed your article for pointing this out π