Mono+Ikvm Runs Eclipse
miguel writes "Today Zoltan Varga announced that he got Eclipse running on Mono using the open source IKVM Java virtual machine for .NET by Jeroen Frijters. This is the first time a complete free software JVM implementation can run eclipse in a reasonable time. This runs with our latest Mono release. Mandatory screenshot"
"One question might be, and I'll be as direct as I can be about this, .Net? Unlike Windows, where you could say it's a product, it .Net briefing day in July
.Net. Things like .Net .Net on a bunch of random
what is
sits in one place, it's got a nice little box. In some senses, it's a
very good question."
- Microsoft CEO Steve Ballmer, at a Microsoft
"We don't have the user-centricity. Until we understand context, which
is way beyond presence -- presence is the most trivial notion of
context."
- Microsoft chairman Bill Gates, on the same topic at the same briefing
"Our biggest problem was policing the use of
Enterprise Servers. That's a great example of where the confusion came
from, because it looked like we were slapping
products."
- Charles Fitzgerald, general manager of Microsoft's platform strategy group,
in August on ZDNet News
"It's about connecting people to people, people to information,
businesses to businesses, businesses to information, and so on. That is
the benefit."
- Steve Ballmer, trying again, in an October interview with News.com
FP?
I also don't see why someone would want to write a JVM for the .NET CLR, perhaps someone wiser than I could enlighten us (after looking on the IKVM FAQ none of these questions were answered partically well.. :)
Two reasons to want a JVM under .Net. First, although there are a lot of Java VMs out there, production grade VMs are not free. If, for some reason, you already have a good .NET setup, it makes perfect sense to leverage it for the odd Java application, rather than spring for an extra Java VM license.
Second, not all Java apps are 100% Java. That's why we have the Java Native Interface, which lets you call native APIs from Java, and also lets you embed Java modules in native-code applications. (A lot of the programming tools in Sun's Java SDK are JNI apps, for obvious reasons.) Now, unless you're going to get all religious and insist that Java and .NET must never contaminate each other. it makes perfect sense for Java and .NET to interoperate using Ikvm, or something like it. Suppose, for example, your boss says that your next project must run under .NET, but won't give you time to port all your Java classes. Or more generally, suppose you're just open minded enough to take the best of both platforms.