And if you manage to write an Erlang => Mono CLI compilier there is no or not much additional work involved to also support the Microsoft CLI.<br><br>On the other side according to my experience Mono shares some problems Erlang has: Decision makers hesitate to use it. Facts or wrong preconception? I think because they do not know it well enough.
<br><br>For many problems I consider Erlang/OTP as the best thing since sliced bread. If only it did not live in its own universe which people do not know and understand.<br><br>Scala and F# are sp far no comparison in my eyes even if they offered a stable distribution mechanism as good as the one in Erlang since they lack all OTP functionality.
<br><br>OK, where is the person who implements a Erlang to JVM and CLI compiler? Unfortunately I don't have the faintest idea what it means to implement such a compiler. Certainly just a weekend job. ;)) At least it must be possible since both, JVM and CLI are supposed to be turing complete.
<br><br>I guess the argument that Erlang's performance will certainly be lower under another VM is right. But won't the advantages (access to .NET or Java, better selling environment) outperform performance penalties? Sell the stuff with low performance, have your foot in the door and if performance becomes critical, use the original Erlang VM.
<br>Oh yes, did I mention that I want it all? ;)<br><br><br>Cheers,<br>your today-not-to-be-taken-serious Michael