Arguments are like
"In OOP, every programming task is solved in a distributed system, adding a layer of complexity". So for the simplest of problems, avoid OOP patterns. Or, if having a complex problem, think about whether adding this layer helps or hinders.
And, perhaps the main subproblem arises about OOP [^1]:
state and identity get mixed up, if state is mutable. Then again, Scala seems to be fine with distributed systems, as many problems even add the actor pattern on top to handle messaging (perhaps not called messaging, that term might be more objective-C-ish) between entities.
------------
1: According to at least Scala's author
And, perhaps the main subproblem arises about OOP [^1]: state and identity get mixed up, if state is mutable. Then again, Scala seems to be fine with distributed systems, as many problems even add the actor pattern on top to handle messaging (perhaps not called messaging, that term might be more objective-C-ish) between entities.
------------ 1: According to at least Scala's author