3 ms·
I can express my OO ideas in erlang with no problem (objects become processes). I cannot express my concurrency ideas-- that erlang makes super easy-- in the O
by nirvana 14y ago
I can express my OO ideas in erlang with no problem (objects become processes).
I cannot express my concurrency ideas-- that erlang makes super easy-- in the OO languages.
Maybe Go changes this but I haven't used Go yet.
- glassx 14y agoAgreed. And Joe Armstrong himself used this argument here: http://www.infoq.com/interviews/johnson-armstrong-oop http://www.infoq.com/interviews/johnson-armstrong-oop
- Ingaz 14y agoAgreed that processes in Erlang is even better objects than objects in OOP. >>I cannot express my concurrency ideas-- that erlang makes super easy-- in the OO languages. In fact main Erlang ideas are many times "stolen". I discover Erlang in: Scala (obvious), F# (also obvious), D (also obvious). Actors + messaging = "DIY Erlang". Although I do not know a language that makes code hotswapping as fundamental feature.