Re^2: Spoiled by Perl (JVM/CLR)

The Java/Microsoft fight of twenty years ago has left us today with what looks to me like an unfortunate legacy: extra work for language implementors ... or is it an extra challenge with the potential to improve the way languages are implemented?

AFAIK, Perl 5 has never seriously run on JVM or CLR. Though Raku has a JVM implementation, the CLR implementation (Niecza) seems to be abandoned. While Python 2 runs on both (Jython, IronPython), the Python 3 port to both these VMs appears to be unfinished - 13 years after the C version of Python 3 was released in 2008!

Note that I don't have any first hand experience here ... opinions/corrections welcome. :)

References

Java Virtual Machine (wikipedia)
List of JVM languages (wikipedia)
Common Language Runtime (wikipedia)
List of CLI languages (wikipedia)
Common Language Infrastructure (wikipedia)
Standard Libraries (CLI) (wikipedia)

Raku Compilers
CPython (wikipedia)
Jython (wikipedia)
IronPython (wikipedia)
History of Python (wikipedia)

Comment on Re^2: Spoiled by Perl (JVM/CLR)

Replies are listed 'Best First'.
Re^3: Spoiled by Perl by Jenda (Abbot) on Dec 07, 2021 at 09:31 UTC
ActiveState used to have tools that allowed you to integrate Perl and CLR based stull. The Perl itself was running using its own engine, but you could call one from the other. It makes more sense to do it that way anyway. CLR was not designed for dynamic languages. Jenda 1984 was supposed to be a warning, not a manual!	[reply]