There are many ways around this, interfaces, strategy factory and repository patterns, he'll even dynamic keyword or il rewriting solutions a lá Jon skeet or even code weaving with AOP solutions.

Although, as you've just posted with your /. handle; you're arguably *not* Anonymous.

I understand what you meant to say; however what you said is different.

Hate to use this line, but please; mod parent up.

I'm convinced anyone who's missing parents point is doing so purposefully.

Good luck brother, I'm personally hoping this turns out to be not such a big deal.

They've refocused SUSE and Mono back to europe; let us hope it doesn't kill the momentum.

Mono is *not* an implementation of .NET, it's an implementation of the CLI.

However, they've already stated that WPF can't work under linux, fair enough ... but from my own experience, I've not authored one piece of .NET software in the last 2 years that needs WPF; I'm pretty sure that no-one in my team has.

Clearly, I'm not the only .NET developer in the world so I welcome your citations ...

You probably know this, but the OP you're quoting just wholesale copied RMSs FSF statement on .NET (linky: http://www.fsf.org/news/dont-depend-on-mono)

I agree with you entirely though, it's FUD.

Erm, Have you actually tried to deploy a .net application recently ?

Other then ensuring that the framework is installed, it is also generally as simple as copying a .exe file.

ClickOnce deployment is vaguely more complicated but its complexities exist to counter security problems. One can hardly blame MS for trying to be a bit more proactive about security either.

The largest (in terms of distribution) .NET program I've ever written had a target audience of roughly 40k computers. Our deployment process ? xcopy or download an MSI file if you weren't on the network.

Which parts of the standard are you referring too ?

Mono does have issues, that's true enough. Microsoft's .Net runtime has issues too.
Linux has issues, Windows has issues ... Everything has issues!

The problem with Mono isn't mono itself (imvho) it's the fact that it's bringing a Microsoft mentality to the GNU mindset and for some people, there can be no compromise on this. That the FSF itself 'discourages' use of Mono can't help matters.

What I'm trying to get at really is that a lot of the negativity towards mono is based on its philosophy and roots, rather then it's technical merit.

Shame really, I'd hoped we were all passed that. Naive, I know!

So one instance of a bug makes the entire thing bad news ?

If that's your tolerance level for using a computer, then perhaps you'd be better with an abacus :)

Then I hope that this all 'comes out in the wash' then.

Ok, I'm not going to wholesale bite but you really need to bring some Citation to this FUD.

You see, a simple google search results in this: http://mono-project.com/Compatibility

Which show's that as far as base libraries and feature support, Mono is almost all there with full .Net 4.0.

Seeing as that's the latest version of .Net and not even the latest version that a lot of businesses are targeting, would suggest that Mono isn't lagging at all.

What about using Google Docs online ?

Me and a colleague have been using them to co-ordinate a contract we're working on and so far, it's been great.

According to his You-tube profile, this guy is from South Korea, not Japan ?

Basically this *shudder*

On the other hand, Meg has accidently introduced us to a great Bass player that I probably would have never experienced.
Props for that :)