17 ms·
> An actor in Erlang is not an object And function with closure and/or with a state passed through and it is an as good as an object. Heck, look at one of the
by rdtsc 12y ago
> An actor in Erlang is not an object
And function with closure and/or with a state passed through and it is an as good as an object.
Heck, look at one of the most popular languages -- Python. Method calls look nice an explicit like def method(self,...). Others have self too (usually called "this"), but it appears there implicitly.
At the memory level Erlang actors are even better objects because they actually enforce memory isolation. Which is in spirit with Alan Kay's original OO idea.
- danieldk 12y agoHeck, look at one of the most popular languages -- Python. Method calls look nice an explicit like def method(self,...). Others have self too (usually called "this"), but it appears there implicitly. "Foolish pupil - objects are merely a poor man's closures." And visa versa. However, this line of reasoning definitely differs from what one nowadays considers an object-oriented language. Which was exactly what this article was about.