From the book "Find Out What Erlang You Have For Great Good:"
Erlang is not a silver bullet and will be especially bad in such as image and signal processing, operating system device drivers, and other functions.
Now, of course, the device drivers of the operating system, but is there any reason Erlang cannot be used to process a digital signal? What does the author mention here? Is it just that Erlang will show poor performance in a DSP application, or is there a special reason why it might be structurally unusable? (I don't think about using it for DSP, I'm just curious.)
It's just that Erlang will show poor performance in a DSP application.
Not only that: you will also not find many (if any) libraries that will help you with this, and you may find Erlang benefits that are not very useful in these domains. This refers to “number crunching” in general, image and signal processing are just examples.
Although my answer may not be accurate, but I think Erlang is not suitable for “signal processing” for the following reasons (of course, maybe there are more reasons. Feel free to correct me):
, , erlang , . Erlang concurrency , , ( concurrency).
OTOH, erlang , parallelism. - DSP C ( NIF). Erlang - , .
, DSP erlang home turf, erlang DSP ( DSP).