In a recent interview with the online edition of the Austrian daily Newspaper Der Standard, Mono project-lead Miguel de Icaza pleads for a cooperation between Mono and Microsoft's .Net: "I think that the deal should include a technical Mono/.NET collaboration, and even go as far as Microsoft recommending Mono for all of their developers looking at migration."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-06-26
Yes, I know that.
But the point is that the lawyers in Redmond are already evaluating things. MS _will_ eventually stand up and sue OSS for patent violation. Ballmer has to act quite soon if he does not want to appear a total idiot to the Micrposoft shareholders. I bet he'll start with mono - well, ok, just a not so wild guess.
Sorry to say this, but mono was a waste of time from the start. It's too close to the devil, and Novell has seen what happens when you embrace the devil.
Now it's time to talk about Java. It's not too late - thank God ...
Member since:2007-02-22
Member since:2005-11-18
...mono was a waste of time from the start.
Considering C# is an ISO standards based language, I don't think you can say mono was a waste of time. It brings C# to the playing field for platforms other than Windows. If anything, it has allowed people to bring their ASP.NET apps written in C# to Linux based web servers. Yes, we've had Java for a long time and it's run things cross platform, but this is another option for the masses. Besides, there have been plenty of really good apps for Linux written in C# using Mono.
Member since:2005-08-17
I'm sure Java infringes on some MS patents, that's the nature of software patents, everybody who makes software is infringing on someone's patents.
But Java has Sun behind it, sun has money and other patents. So there is a good chance microsoft wouldn't attempt to sue over such patents.
Mono is currently being well supported by Novell, who have a deal with microsoft to licence microsoft patents.
Microsoft suing the Mono project would be very bad for Novell and hardly an advantage for Microsoft as Mono is less of a threat than say, OpenOffice or Firefox.
Member since:2006-01-16
There are two sides of this issue.
Sure, if you don't use these bindings, you aren't affected at all.
The GNOME people seem to get fed up with C. So it is even evaluated to switch to Mono/GTK# as main development platform. This wouldn't be something done today or tomorrow. But GNOME already ships applications using GTK#.
Member since:
2005-07-22
Should they step further into that Microsoft shit - sorry, but that's what it is - I'll switch to KDE
The only connection between Gnome and mono is the GTK# bindings. mono is a cross language runtime and particular bindings for a GUI api are just a side show. You are only tied to Microsoft via mono if you use a Microsoft api such as Windows Forms or ASP.NET. If you use GTK#, Cocoa# or KDE's Qyoto/Kimono bindings (that I work on), you are only tied to the C# language and other CLR languages. The CLR is an ECMA standard, whereas Windows Forms isn't, so please separate issues about using Microsoft specific GUI's from using mono as a basis for implementing interesting non-Microsoft apis via bindings.