"Microsoft today announced its first collaboration with the open source Eclipse Foundation by committing provide engineering support to allow the Eclipse Standard Widget Toolkit use Microsoft's Windows Presentation Foundation. The move aims to make it easier for Java developers to write applications that look and feel like native Windows Vista, according to Microsoft."
To read all comments associated with this story, please click here.
Member since:2007-06-29
Member since:2007-02-05
There are many situations where it makes sense to work with managed code.
Typically applications that used to be VBA(in Access, adp-style. Connected to server, not using local db files obviously) are now often being ported to .NET
Aside from the fact that Microsoft slowly have been killing proper SQL-connectivity support in Access it makes sense. .NET is quite faster than VBA, they can write in a language that's quite familiar, popular(means more peopel and more resources.)
These are typicaly making programs such as project manegemant systems(for instance for the Oil Bussiness). None of these gives a rat's ass if these programs don't run faster than Lynx, all they care about is that it is easy to program, and get working. (Managed code may be slow but it's easier to avoid bugs, and easier to debug.)
In my experience I've found .NET to be faster than Java. Might been bad/good luck, but it wouldn't suprise me if that's the case. After all... .NET is prettymuch a ripoff after Java, only that it's made after Java so they could see what mistakes where made in Java and fix them from the start. (Not dissing Java though, it was in it's time quite a excellent idea! And it has multiplattform wich MS has chosen for obvious reasons not to implement in .NET)
Now, making 3D Studio Max in Java or .NET is probably not a good idea... but there are uses for managed code.
Member since:2005-07-14
Except, of course, that .NET apps are fast and look/feel like "native" applications, on XP at least. I've been using Paint.NET (for example) at work, and there doesn't seem to be any slow-down or anything due to it being managed code.
Compared to Eclipse, it feels like it's been written in pure assembly language.
I like Eclipse (it crashes less than VisualStudio, at least for me), I just wish it was faster.
This seems like a weird move for MS.
Member since:2005-07-06
That is incorrect. MS's implementation of Java wasn't able to pass Sun's compliancy test due to it having Windows only hooks...it had nothing to do with the way the software it created 'looked' or whatnot.
http://en.wikipedia.org/wiki/J%2B%2B#Litigation_against_J.2...
Member since:2005-07-06
Indeed... people try to make it sound like the MS lawsuit was about MS wanting to extend java. In reality the lawsuit wasn't so much about that as it was MS's desire to extend it in ways that caused Sun compatible Java apps to fail when run on MS VMs.
MS refused to fix the issues, and thus the lawsuit.
Member since:
2005-07-05
The whole point of Sun's lawsuit against Microsoft back in the 90s was that Microsoft was trying to add stuff to Java that would make Java programs look more like Windows programs, with the negative side effect that Java programs written for Windows would not run on other platforms.
I wonder why Microsoft didn't just do something like this back then; assuming that tying in this way will still allow Java programs written to look like Vista programs to run unaltered on other platforms?
This does beg the question, who in their right mind uses Java to write desktop applications? But that's another issue all together.