Has OO done more harm than good?

@ewolff wrong question. oo is a perfectly valid paradigm. neutral by default. people misinterpreting and/or misusing it may cause harm

. @ufried OO promotes shared state. Bad for concurrency. OO proposes common models. Bad for scaling development.

. @ewolff dunno. an akka actor is basically a pure object: encapsulating state and behavior. comm. via messages. fits perfectly. no probs

@ufried @ewolff You could reasonably argue an actor is more of an object than an instance of a Java or C++ class

@stilkov @ufried OK - show me classes and inheritance in an actor model.

@ewolff @ufried Still, a Smalltalk message is in many ways more like a message to an actor than a virtual method invocation.

@stilkov @ufried Judging by userpage.fu-berlin.de/~ram/p… you are probably right. However, I could argue a Microservice is like an Object, too.