4 ms·
Interestingly Erlang creators saw the problem and solved in a practical way a while back. It was funny in that they didn't go read academic literature, they had
by rdtsc 12y ago
Interestingly Erlang creators saw the problem and solved in a practical way a while back. It was funny in that they didn't go read academic literature, they hadn't even heard about the "actor model". They just realized that they needed to minimize large mutable states in concurrent programs. Variables are single assignment, data is immutable. One object (actor) crashing doesn't impact others. Then eventually later someone said "hey that's the actor model you are using".
They also didn't set out to create a functional language explicitly. They didn't know about monads, applicative, functors etc.
Another funny anectode, Joe Armstrong is quite fond of calling Erlang the only true OO language in its original sense. The idea of methods being messages sent between isolated and opaque objects. This isolation is really enforced at the heap level and methods are really messages being send to an actor's mailbox.
If you listen to Alan Kay, he mostly agrees:
http://userpage.fu-berlin.de/~ram/pub/pub_jf47ht81Ht/doc_kay_oop_en http://userpage.fu-berlin.de/~ram/pub/pub_jf47ht81Ht/doc_kay...
---
OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things. It can be done in Smalltalk and in LISP. There are possibly other systems in which this is possible, but I'm not aware of them.
Cheers,
Alan
---
- CmonDev 12y agoVery true, also Erlang is different from pure Actor Model AFAIK because it provides certain guarantees that messages will be ordered, unlike: http://en.wikipedia.org/wiki/Actor_model#No_requirement_on_order_of_message_arrival http://en.wikipedia.org/wiki/Actor_model#No_requirement_on_o...
- angersock 12y agoI've heard it put that Erlang was created to solve the issues of distributed system, and as a result, solved concurrency for free. I really like it because it feels like it was meant to do something other than pad out a thesis--it's probably the only functional language other than F# or LINQ to do that.