[erlang-questions] Dirty NIF - classifying as CPU or I/O bound

[Roger Lipscombe]

On 14 October 2018 at 14:44, Stanislaw Klekot <erlang.org@REDACTED>
wrote:

> Why do you insist on using ill-suited mechanism of NIFs that will
> most probably destablilize your BEAM machine? Ports were designed
> specifically so you can easily run foreign code without causing problems
> to the VM.


Why do you insist on *telling me something that I already know*? Assume
that there are other things going on (that I'm not going to tell you about,
because they're not relevant to the question) that make using a NIF the
right trade-off even with the stability risks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20181014/0d1b30f9/attachment.htm>