[erlang-questions] Dirty NIF - classifying as CPU or I/O bound
Sun Oct 14 15:44:48 CEST 2018
On Sun, Oct 14, 2018 at 02:03:21PM +0100, Roger Lipscombe wrote:
> On 14 October 2018 at 13:49, Stanislaw Klekot <erlang.org@REDACTED>
> > If you execute a third party code you have no control over, you don't
> > execute it as NIF, but as a separate program through a port (or maybe as
> > a C node). NIFs are not a solution for each and all problems in Erlang.
> I'm aware of the risks. Assume that I'm accepting them.
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.
More information about the erlang-questions