Interesting. A huge part of the Erlang value proposition is that the language and runtime are designed to complement each other, and both have significant constraints imposed by the language design.
Taking half of that equation, and supporting any language, feels like you’re missing a big part of the benefit.
How exactly is Erlang complimenting BEAM in a way that Elixir, for example, doesn’t?
The other languages that work with the BEAM are all roughly equivalent. I failed to be explicit, but as weatherlight indicated, languages like Ruby will never work on it.
But your argument is “supporting any language”. Lunatic isn’t supporting any language, the language has to be compatible with WebAssembly for all the reasons you and weatherlight stated.
Not to be pedantic but Ruby has webassembly support, still won't work on the BEAM.