Linked by David Adams on Thu 18th Dec 2008 23:07 UTC, submitted by ebasconp
I read in InfoQ: "Ja.NET is a port of Java 1.5 SE to the .NET platform. The compiler is based on the Eclipse JDT, which has been modified to generate IL as well as Java Byte Code. Java traditionally compiles each class into a separate file, but this creates an unacceptable overhead for .NET. To address this, a tool based on Cecil is used to create larger assemblies much in the same way Jar files are created for Java."
Thread beginning with comment 340771
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:2006-08-02
The "reverse" already exists - Jacil (http://sourceforge.net/projects/jacil).
Also these days .NET is part of Windows, while the JRE is an addon - someone distributing Java applications might want to distribute native looking .EXEs to Windows users instead of requiring an additional download.
Recent versions of Java only support Windows >= 2000. .NET supports some older versions of Windows so it could a useful way to port Java software to unsupported versions of Windows.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-05-09
Why not implementing a C# compiler that generates bytecodes instead of IL or a CLR implemented in Java instead of the inverse?
Though the idea seems to be amazing and very interesting, I think it shows where the balance is getting biased...