Linked by Thom Holwerda on Mon 13th Dec 2010 19:27 UTC, submitted by lemur2
Mono Project For the most time, I've been firmly in the largest camp when it comes to the Mono debate - the 'I don't care'-camp. With patent lawsuits being hotter than Lady Gaga right now, that changed. For good reason, so it seems; while firmly in the 'ZOMG-MICROSOFT-IS-T3H-EVILL!1!!ONE!'-camp, investigated the five most popular Mono applications, and the conclusion is clear: all of them implement a lot of namespaces which are not covered by Microsoft's community promise thing.
Permalink for comment 453423
To read all comments associated with this story, please click here.
Some things to consider
by isaks on Tue 14th Dec 2010 07:48 UTC
Member since:

It seems nobody has pointed out the obvious that a line 'using Some.Namespace' has nothing to do with whether or not functionality from that namespace is used or not.

Ok, 'nothing' is a bit harsh, but consider:
1. 'using Foo.Bar' is only a shorthand to not have to type the full qualifyer each time (eg 'new Foo.Bar.Baz()' vs. just 'new Baz()')
2. IDE's tend to give you the boilerplate using-statements at the top when you create a new class leaving you with a few unused 'using'-statements at the top.

Reply Score: 2