[erlang-questions] Erlang and Akka

Youngkin, Rich richard.youngkin@REDACTED
Tue Sep 2 16:39:17 CEST 2014

>> On 08/28, Xiao Jia wrote:
>> But in such languages as C++/Java/... we are not forced to mutate
>> so we can still employ some coding style/guidance of creating new objects
>> instead of mutating existing objects most of the time.

On 8/28 Fred Hebert wrote:
> Ah but did the people writing the libraries you use think the same way?
> One of the advantages of Erlang is that because of its constraints,
> *everyone* programming in it ends up making decisions that are generally
> amenable to concurrency and to some extent, distribution. Those who
> don't tend to make libraries that hardly scale on a single node to begin
> with (with heavy bottlenecks and whatnot).


Is this true of Erlang libraries that use NIFs and or Port drivers?
Specifically, I'm thinking of blocking the VM scheduler(s).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140902/e2da9397/attachment.htm>

More information about the erlang-questions mailing list