@tenderlove @bascule @thisismissem I'm not sure I agree on the concept. Rust is, quite famously, well suitable for embedded devices full of unsafe code--I scrapped my own Ruby-like language that was too much like Rust in favor of pre-1.0 Rust--where you do need to consider the same concerns
interoperability with other languages is in the same area. just like with MCUs, someone needs to implement the interop once and others can (safely!) reuse it later
@tenderlove @bascule@mas.to @thisismissem I think it should be entirely feasible to write a Rust library that obviates the need to understand the generated machine code. this isn't actually specific to Rust, it appears in C++ too--if you look at something like V8 or TraceMonkey, which are written in C++, they wrap references to the JS values in a RAII pointer like @bascule suggests, for the exact same reason
Ruby is just being fast and loose in its API