3 ms·
Call me a skeptic, but this project ditches Erlang's awesome VM and takes only the clunky language syntax and puts it on the JVM. I wonder how things like proc
by vladev 17y ago
Call me a skeptic, but this project ditches Erlang's awesome VM and takes only the clunky language syntax and puts it on the JVM.
I wonder how things like process isolation will work out.
- sriramk 17y agoYou beat me to it. My first reaction was "Wait - how is preserving Erlang's syntax but losing the VM a good thing?". I'd love projects going the other direction - a more modern syntax built on Erlang's rock-solid VM + OTP libraries.
- bad_user 17y agoI don't see a problem with process isolation ... you can control the bytecode generated from the compiler, and then you make the Java FFI really hard to please. Since Erlang uses light-weight processes, this is exactly what the Erlang VM is doing.
- xtho 17y agoI'm always skeptic if there is only one actively maintained implementation of a language in use. In this respect, this is per se a good thing.