http://www.sics.se/~joe/bluetail/vol1/v1_oo.html
Erlang is closer to original Smalltalk than most of current OO languages: there are processes (objects) which communicate by messages (messages).
I also should mention OOHaskell: http://homepages.cwi.nl/~ralf/OOHaskell/ "In the second and major phase, we systematically substantiate that Haskell~98, with some common extensions, supports all the conventional OO features plus more advanced ones, including first-class lexically scoped classes, implicitly polymorphic classes, flexible multiple inheritance, safe downcasts and safe co-variant arguments. Haskell indeed can support width and depth, structural and nominal subtyping. We address the particular challenge to preserve Haskell's type inference even for objects and object-operating functions. Advanced type inference is a strength of Haskell that is worth preserving. Many of the features we get ``for free'': the type system of Haskell turns out to be a great help and a guide rather than a hindrance."
So everyone "can has" his OO everywhere, in case one needs it.
[1] http://en.wikipedia.org/wiki/Specification_and_Description_L...
It's more like "I know how OO allow teams to work together. I don't know how functional programming does that".
What would be the answer to that?
erlang is designed around intercommunication, there was some rule about how a team of 3 would make a 3 pass compiler, in erlang everything is explicitly isolated and you have to design specifically how the various parts of the system communicate with each other
> I can’t imagine how you can organize large code-bases in Erlang or even work as team, and this doesn’t feel right to any OO programmer.
Well, yeah, but neither would Clojure or Haskell or a host of other interesting and useful languages. Functional programming is a completely different paradigm, and if you come into with an OO mindset the results will not be good. But that's more a fault of the programmer than the language.