I think Efene/Ifene is better for this task (just different syntax for Erlang, without changing Erlang semantics). No performance overhead.
Reia has completely new semantics and run in interpreted mode over BEAM (Erlang VM).
I personally think, that if programmer can't adapt to new syntax, it will be much harder to her/him to adapt to new semantics.
Erlang's syntax is ugly comparing to modern languages like Ruby. The simple things are hard to do in Erlang and simple in Ruby, but complex thing are easy in Erlang and impossible in Ruby.
Erlang is pragmatic choice for today. Maybe in 5-10 years Erjang,Scala,Go,Rust or some other new language will be a better choice, but until then use Erlang/OTP.
Reia isn't "interpreted" in any manner different from the Erlang language itself. It's somewhat similar to CoffeeScript in that it uses parse transforms to produce Erlang parse trees which are then compiled by the Erlang compiler just like any other Erlang source code. However, it's a bit more like JRuby in that it ships a runtime, core types, and a standard library.
It's slower than Erlang, not because it's executed in a different manner than Erlang, but because it supplies a separate late binding mechanism for dispatching methods to their receivers.
Reia has completely new semantics and run in interpreted mode over BEAM (Erlang VM).
I personally think, that if programmer can't adapt to new syntax, it will be much harder to her/him to adapt to new semantics.
Erlang's syntax is ugly comparing to modern languages like Ruby. The simple things are hard to do in Erlang and simple in Ruby, but complex thing are easy in Erlang and impossible in Ruby.
Erlang is pragmatic choice for today. Maybe in 5-10 years Erjang,Scala,Go,Rust or some other new language will be a better choice, but until then use Erlang/OTP.