Has OO done more harm than good?
3
1
2
@ewolff wrong question. oo is a perfectly valid paradigm. neutral by default. people misinterpreting and/or misusing it may cause harm
1
4
. @ufried OO promotes shared state. Bad for concurrency. OO proposes common models. Bad for scaling development.
5
4
. @ewolff dunno. an akka actor is basically a pure object: encapsulating state and behavior. comm. via messages. fits perfectly. no probs
3
2
@ufried @ewolff You could reasonably argue an actor is more of an object than an instance of a Java or C++ class
6
3
4
@stilkov @ufried OK - show me classes and inheritance in an actor model.
2
Replying to @ewolff
@ewolff @ufried Still, a Smalltalk message is in many ways more like a message to an actor than a virtual method invocation.

Sep 19, 2015 · 7:53 PM UTC

1
1
Replying to @stilkov
@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.
3
2
3
@ewolff @ufried Nice reference, thanks for digging it up.
1
1