Even a Rust NIF is too much for a bunch of people, so that’s the difference and the selling point for many in the BEAM ecosystem.
While I don’t share that skepticism (my SQLite library that heavily steps on a Rust NIF is still coming sometime this year and not like it’s not been 99% done for months, I am just burning tokens to find problems in it before my users do), I also get it because theoretically you throw away BEAM’s stability guarantees, and how many people truly inspect their Rust code for .unwrap() and .expect()?
Cloudflare themselves made that mistake.
Even worse, how many people heavily audit their C code for use-afrer-free / double-free et. al.?
Pure Elixir alternatives, even if they end up 50x slower – @manuel-rubio, I make ZERO claims about your excellent tool, just raising a hypothetical – many people would welcome NIF-free dependencies for what is viewed as a necessary evil by many otherwise.
