Yup, and dirty NIFs for long running(>1ms) are just around the corner in BEAM.
> And I'm kinda avoiding that on a quad core CPU your
> C program is really going to only use one core out
> of the box while elixir will use all four.)
I think that's a pretty major factor to avoid -- multicore processors are the immediate/commercial foreseeable future of CPUs, so its not inconsequential that Erlang/Elixir allow you to be able to use cheap processes in order take full advantage of this
https://github.com/elixir-lang/elixir/wiki/Interoperability-...