Linked by Thom Holwerda on Fri 12th Jun 2009 18:25 UTC
Permalink for comment 368426
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 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-03-11
Don't like Mono? Don't install it. . .
All that is fine and I would agree, but that is NOTwhat this is about. The article is about mono being included by DEFAULT. Problem is that you can't just remove mono and the associated apps as this will cause problems when doing updates due to a meta package being missing.
It is pretty much a given that there is some question as to Mono and patents, at least in the US. MS seems to suggest that it has some "IP" associated with it as it entered into a patent sharing contract with Novel. MS won't clarify the issue. Based on that alone it seems foolish to include this software by default.
How hard it is to install this mono encumber software after the base desktop is installed? It isn't . . . so why would it be necessary to include it in the base. If it is so important put a big flag on the default desktop about how to install it, problem solved and I don't have to worry about mono.
It seems like an easy answer to me.
BTW I don't want mono installed by default, it just encourages the use of it for projects. IF MS comes out and puts it in writing that mono is not patent/IP encumbered I don't have a problem using it. Although, it does seem rather bloated as is the usual with anything associated with MS. 8^)