Message-passing is a fundamental part of Erlang. Alan Kay has argued that message-passing is a concept more important than objects in his view of object-oriented programming (and he "invented" the term!).
Can Erlang be considered an object-oriented programming language (à la Smalltalk)?
Erlang is OOP in its purest form. Unlike more mainstream languages, it focuses on the core idea of OOP — messaging. In Erlang, objects communicate by passing immutable messages between objects.
Unlike objects in Java, Ruby or other so-called “object oriented” languages, Erlang processes are fully isolated from one another, so much so that catastrophic failure in one process does not spell disaster for all the others.
Ruby is a pure object-oriented language and everything appears to Ruby as an object. Every value in Ruby is an object, even the most primitive things: strings, numbers and even true and false.
JavaScript is not a class-based object-oriented language. But it still has ways of using object oriented programming (OOP). In this tutorial, I'll explain OOP and show you how to use it. The most popular model of OOP is class-based.
Joe Armstrong has gone on record saying that he thinks that Erlang is "possibly the only object-oriented language" (the context adds "OO in the Alan Kay meaning of the word"). Johnson, in the same interview, points out the same things that Sean Copenhaver says in his answer: in the small, Erlang's a purely functional language; in the large, with processes, it looks exactly like Kay-style object orientation.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With