Linked by Thom Holwerda on Thu 27th Sep 2007 07:55 UTC, submitted by Augusto
Permalink for comment 275102
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
Linked by Thom Holwerda on 06/14/13 11:39 UTC
Linked by Thom Holwerda on 06/14/13 11:32 UTC
Linked by Thom Holwerda on 06/13/13 19:39 UTC
Linked by Thom Holwerda on 06/13/13 14:45 UTC
Linked by Thom Holwerda on 06/13/13 11:43 UTC
More News »
Sponsored Links



Member since:
2005-08-31
This is what matter most. They politically said ( it's not a pragmatic programmer literature where the exact meaning of the sentence is the clear answer), maybe we used Microsoft patent, maybe we will also lose in court, so even if we think and say we dont, we'll take no chance and give them (Microsoft) what they want.
I think Novell should split mono in two parts. First, they have two incompatibles goals. [Mono provides the necessary software to develop and run .NET client and server applications on Linux, Solaris, Mac OS X, Windows, and Unix ....] AND […. positioned to become the leading choice for development of Linux applications.] http://www.mono-project.com/Main_Page
The first one is a corporate goal to lower cost of software migration to other OS. The other one involve creating a community that use there tool to build free solution. A community that want open standard without patent restriction. But yet Novell promote the use of ADO.net and ASP.net even if they explaining in there FAQs that they’re patents restricted technologies. [… potential issues that might arise with ASP.NET, ADO.NET or Windows.Forms]
My solution would be to make all the microsoft high level blocks ship as a separated package for .net interoperability. and sign an agreement -only- on that part, even charge for it. This would satisfy the first goal without compromising the second one.
Then, Novell/mono should encourage open source new technologies base on the CLI. Which is a great technology, combine with the boo language, I would probably jump in. Anyway, solution like Django or pylons are superior of ASP.net, sqlalchemy or db4o is also a step forward ADO.net and wxsharp and gtk are quality substitute for winform. Mono needs the community to perceive them as a technology innovator and not a submissive follower where using they’re product is a potential danger.