Clojerl is really cool, and you should play with it; it's actually surprising how well the semantics transfer over to the Erlang VM.<p>If anyone wants something that feels a bit more vanilla-erlang-ish, one should also check out Lisp Flavoured Erlang. It is almost a direct one-to-one translation of Erlang into Lisp-land (actually made by one of Erlang's co-creators), but also provides Common-Lisp-Style macros, and a much more consistent, cleaner syntax than vanilla Erlang.
With the ability to reach Java, JavaScript, .Net, and Erlang runtimes, plus interop with many other languages via GraalVM, Clojure has incredible reach across runtimes, perhaps more than any other modern programming language, certainly among Lisps. That said, its pretty gnarly to try to navigate all of the implementation differences among platforms. I wonder if there is a subset of Clojure that is 'safe' to run on any of its supported environments.<p>This list is pretty long:
<a href="https://clojerl.github.io/differences-with-clojure/" rel="nofollow">https://clojerl.github.io/differences-with-clojure/</a><p>For now, the JVM is the only way to get the full Clojure experience.
There are at least 19 alternative languages for the BEAM[1]. If anyone knows of any I’ve missed, let me know.<p>[1]: <a href="https://gist.github.com/macintux/6349828#alternative-languages-targeting-the-erlang-vm" rel="nofollow">https://gist.github.com/macintux/6349828#alternative-languag...</a>
The site does a great job explaining what Clojure features exist in this port ... but what about Erlang features? There doesn't appear to be a first-class adoption of things like supervisors and actors like you see in Elixir, for example. Or at least the docs don't do a great job explaining it?
Page is a frameset around <a href="https://clojerl.github.io" rel="nofollow">https://clojerl.github.io</a>, which breaks the mobile experience (fixed width, content too small). Going directly to the github.io copy scales the content correctly and provides https.
I don't see how this brings anything new to the ecosystem. Clojure is a LISP and we already have lfe (<a href="http://lfe.io/" rel="nofollow">http://lfe.io/</a>) - LISP floured Erlang for quiet a while now, hence it will definitely be more mature than a new implementation altogether. Moreover I feel, seeing the the currently more effort should be made in maturing the classic clojure implementation and the tooling around it itself, rather than diverting the community into fancy new (not so useful) ports of the same syntax for other runtimes. Seriously, just go improve clojure itself. And if you want to be able to write lisp for BEAM, just use lfe.