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
@ufried But I largely agree with @ewolff: OO was built with a single-thread, single-core assumption

Sep 19, 2015 · 7:50 PM UTC

2
2