4 ms·
IMHO, it's the "open" part and less the "source" part. I believe a lot of projects were reluctant to jump on the Mono train because they expected it would be st
by mdaniel 12y ago
IMHO, it's the "open" part and less the "source" part. I believe a lot of projects were reluctant to jump on the Mono train because they expected it would be steamrolled (on purpose or just through sheer manpower) by the .NET. However, if everyone is building on top of the same CoreCLR, it's possible that fear might subside. I doubt it will ever go away because Microsoft will continue to keep some APIs close to the vest.
If it's possible to transpile either Java source or better Java class files to a CLR assembly, even some of the community momentum that Java has might turn into a benefit for .NET, too.
- wtetzner 12y agoI think this is what you're looking for: http://www.ikvm.net/ http://www.ikvm.net/ In particular: http://sourceforge.net/p/ikvm/wiki/Ikvmc/ http://sourceforge.net/p/ikvm/wiki/Ikvmc/
- mdaniel 12y agoI had heard of such projects back in the day, but didn't know if they were still in service (and I didn't take the time to research it). I had some skepticism about whether IKVM had kept up with the rapid moving target that is the JRE, but after seeing that it runs Minecraft[0], I'm guessing it'll likely be alright :-) But holy shit, who in their right mind still uses CVS?! 0 = http://weblog.ikvm.net/default.aspx?date=2014-12-01 http://weblog.ikvm.net/default.aspx?date=2014-12-01
- floatboth 12y agoOpenBSD uses CVS :-)
- Rapzid 12y agoA lot of successful .NET projects are based on converting Java to C#, such as NGit.