[erlang-questions] Erlang vs Clojure

[Ludovic Coquelle]

And mono support already F#.
What is the advantage to port Erlang VM to any other VM (JVM or CLR of
.NET)? the fault-tolerant behaviour of Erlang is mainly due to its VM, isn't
it so?

If we are looking only at the message passing model in JVM, scala implements
it completely (I may be wrong), and it may be easier to implement the
distribution on Scala than the whole Erlang VM. You can replace Scala by F#
and JVM by CLR in previous sentence ;)

I like the idea of JVM (and the CLR yet better), but I think the current
advantage of Erlang is the stable state of its VM and the OTP library.
Wouldn't we loose that if we are doing Erlang on any other VM?

Please, tell me where I'm wrong, I would love to have Erlang on any other VM
supporting lots of libraries ... this would remove all reason to not use
Erlang :)

On 11/28/07, Ulf Wiger (TN/EAB) <ulf.wiger@REDACTED> wrote:
>
> Michael Regen skrev:
> > Hi,
> >
> > Don't want to break the current thread  about lispy Erlang and realtime
> > support but there is just a thought about the initial question I need to
> > get off my chest.
> >  > Does anyone see the benefit of a Lispy version of Erlang on the JVM?
> >
> > I would see two huge benefits if Erlang as it is today would run on the
> JVM:
> >
> > a) Much easier to call Java from Erlang. JInterface works but is not
> > really what I want to sell as the future. Besides, why reinvent the
> > wheel - Java has so much to offer.
>
> Another candidate VM is of course Mono (open source version of .NET)
>
> http://www.mono-project.com/Main_Page
>
> BR,
> Ulf W
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20071128/4b20c40d/attachment.htm>