Linked by David Adams on Thu 18th Dec 2008 23:07 UTC, submitted by ebasconp
Java 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 340761
To read all comments associated with this story, please click here.
Whats the point
by Matzon on Thu 18th Dec 2008 23:22 UTC
Matzon
Member since:
2005-07-06

Cool, but whats the point?
I fail to see why I would ever use it?

Both Java & .NET are available on the Windows platform - why would I use a runtime that is very likely to be incomplete?

RE: Whats the point
by google_ninja on Thu 18th Dec 2008 23:24 in reply to "Whats the point"
google_ninja Member since:
2006-02-05

IL interop is top knotch, so if you want to use a java library in your .net code, this would be a great way to do it.

Reply Parent Bookmark Score: 4

RE: Whats the point
by Almafeta on Mon 22nd Dec 2008 00:15 in reply to "Whats the point"
Almafeta Member since:
2007-02-22

Cool, but whats the point? I fail to see why I would ever use it?


Because a big part of why .NET is used in the first place is that it can run code written just about every language.

Of all the languages I know, the only one that doesn't have a .NET port yet is Ada, and they're working on it. (Erm... wait. Actually, there is an Ada .NET port, A#, which I found when I googled it up, so scratch that...)

Reply Parent Bookmark Score: 2