3 ms·
What Erlang brings you is precisely that... "And then got messy because they stopped using messages for some side channel communication." ... can't happen in
by jerf 15y ago
What Erlang brings you is precisely that...
"And then got messy because they stopped using messages for some side channel communication."
... can't happen in pure-Erlang code. Of course there's nothing you can do in Erlang or Haskell that you can't do in pure C, but the problem is that if you are working in C you can't ever quite be sure that something somewhere accidentally mutated a value, when the language makes it so easy. (And let's not talk about C++.) Some of the Haskell leaders call it "wearing the hair shirt".
This is extended agreement, by the way, not a disagreement. If you are stuck in C, there are far worse things you can do that try to impose your own message-passing paradigm, just as there are an awful lot of object-oriented C programs in the world.
- Retric 15y ago"an awful lot of object-oriented C programs in the world" IMO, the good parts of object-oriented programming was applying the constraints of mulithreaded messaging passing to the single threaded world. Really clean multithreaded code tends to be extremely decoupled and treat each message is something to be decoded not blindly followed. Yet somehow that fell to the point where using lots of getter/setter are considered acceptable. PS: That could actually be a good metric how many objects do you use that don't have a single getter or setter.