[erlang-questions] enif_send from a thread after NIF returns

[Joel Reymont]

On Oct 25, 2010, at 6:51 PM, Paul Davis wrote:

> For instance, if you had a situation that could be solved as a port
> using the async thread pool, why would you want to re-implement that
> as a NIF?

I think it boils down to ease of use and to "worse is better". 

Yes, NIF requires reimplementing an async thread pool but NIF is so much easier to use!

Want to debug your NIF? Attach a debugger and you are there. The layer between the Erlang VM and your C code is thin and transparent! Compare this to trying to debug a port driver, even if you manage to fully understand it's underlying mechanisms.

---
http://twitter.com/wagerlabs