News for hackers. Stuff that matters.
Re:The unintentional side-effects of a bad concurrency model by it on Tuesday January 26, 2016 @07:00PM (#10977224)
Erlang doesn't require any programming effort to parse and marshal messages. You just send them and receive them.

  Pid ! {hello, world}

  receive
     {hello, world} ->
        io:format("Received hello.~n", [])
  end
Re:The unintentional side-effects of a bad concurrency model by _yosefk on Wednesday January 27, 2016 @04:20AM (#10979088)
There's a lot of machine effort though, if the data structures are big. If you're doing computer graphics or vision and you have to send images or 3D assets around, it won't perform very well. I think Armstrong consistently underestimates the cost of messaging compared to shared memory - or rather the fact that systems where this cost is prohibitive exist, just as much as systems where his approach works great exist.