Linked by Thom Holwerda on Wed 7th Mar 2007 22:27 UTC
Java "Although the .NET vs. Java war is basically over for control of the Windows desktop, where .NET is sure to become the managed language of choice for new Windows desktop applications, there is a new battle brewing. That battle is for the Linux desktop. Now that Java has been open sourced under the GPL, even the most strict of the 'free software only' distributions can start bundling it and integrating it into their Linux distributions out of the box."
Thread beginning with comment 219488
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Only Two Choices?
by kaiwai on Thu 8th Mar 2007 01:26 UTC in reply to "RE: Only Two Choices?"
kaiwai
Member since:
2005-07-06

That and because of the fact that Mono's class libraries use the MIT license, there are potential software patent traps.

Not entirely true; the core classes along with GTK#, Cairo# and friends are ok - the problem with occur with the .NET compatibility like Winforms.

Then again, its no more troubling than Wine, which probably treads on a number of patents and yet, there isn't a single bit of protest.

Microsoft know that ultimately Mono will always be playing catch up; the VM of mono alone is immature and no where near the capabilities of Microsofts own .NET or Sun's Java VM - and given that the development is done by only one company, Novell, and a cheapskate organisation at that (unwilling to spend money when required) Microsoft know that its always going to nothing more than a novelty.

Reply Parent Score: 5

RE[3]: Only Two Choices?
by g2devi on Thu 8th Mar 2007 20:55 in reply to "RE[2]: Only Two Choices?"
g2devi Member since:
2005-07-09

> Then again, its no more troubling than Wine, which
> probably treads on a number of patents and yet, there
> isn't a single bit of protest.

Actually not quite correct. Everyone recognizes that WINE and Winelib are temporary (imperfect) solutions, not permanent ones, so the effect of a patent trap is less because few people rely too heavily on WINE. If worse comes to worse and the trap is sprung, you can always use VMWare/Xen/KVM/QEMU.

When Corel ported Wordperfect to Winelib, people balked, so I wouldn't say there isn't a single bit of protest for WINE.

The key difference between WINE/Winelib and Winforms/ASP.NET/ADO.NET is that the later is billed as a permanent solution to writing portable apps that can be developed on Windows first while the former is not.

Edited 2007-03-08 20:57

Reply Parent Score: 5

RE[4]: Only Two Choices?
by kaiwai on Thu 8th Mar 2007 21:12 in reply to "RE[3]: Only Two Choices?"
kaiwai Member since:
2005-07-06

Although I'd like to see Wine as a temporary solution, the reality is anything but that.

When you have lazy software companies like Adobe not getting off their ass porting their software to Linux, knowing full well that that there is a massive demand, both by Windows and MacOS X users looking at migrating, Wine unfortunately by the nature of laziness of software companies, will become a perminant fixture on the Linux desktop.

Now, I'm not trying to scare people, but it does open up a big can of worms, and worse still, due to the crap portable nature of Wine - the fact that its severly broken on any platform outside Linux - try running it on FreeBSD or Solaris for example, you'll always end up getting locked into a single operating system - hence my preference for an opensource replacement; atleast then I can move and take the application with me, if I move from Linux to FreeBSD, as long as the application as been ported, I can continue on running the same one - with wine, its the roll of the dice as to whether something that might have run under wine on Linux runs under wine on FreeBSD or Solaris.

Reply Parent Score: 3