Link Details

Afff! Flame war again!

Yeah, yeah....when .Net starts running on real OSes than I will star to worry...
,

Does mono fail for you?

MS is ahead because it has competent people designing the language, libraries and tools. Though of course there are grave errors in there, for example, MSDN docs are a huge step back from javadoc in navigability.

Yes it does. Please show me a decent sized working cross-platform mono app. Seriously. Performance is lousy, the framework is spotty, the tools are almost non-existent.

M$ is still in drain circling mode.

monodevelop

Microsoft is on track again, They have the best tools, the best languages, the best infrastructure, the best GUI and client side development and their serverside offerings are getting great and they got now even ASP.Net mvc with jQuery.

Java is felling down and now with Swing deprecated it will be worst, Javafx sucks big time and it is getting a mess, Java is only good on the server side,
I'm thinking very seriously to go back to Microsoft offerings.

I don't care the cross-platform because everything is Windows, Linux already failed on the desktop, Windows have a lot of ground on the servers and data centers, Macs are just a niche, I dont see where we need the cross platform development anymore, Unix is dead, Linux killed Unix.

C#.Net is the way to go now.

The cross platform argument of many Java developers is naive, at best. I agree with OtengiM in that Java was only ever good on the server side. Java applets were a joke and development in Swing was plain awful. The Winform projects I've built and worked on have been an extreme pleasure and with advancements in WPF & Silverlight, client side development in .NET is only getting better and better. The WCF framework is simply amazing and I know of nothing in the Java community that even comes close. And lastly, I've been more than pleased with the results of the ASP.NET MVC framework (which will ship with jQuery).

Microsoft has had its fair share of bad products (e.g., SharePoint), but the .NET framework has always been very solid. Personally, I am not a fan of duck typing (new in the C# 4.0 language specification through the dynamic keyword), but with a few minor exceptions, both the language and the framework has continued to impress me with each release.

@senfo yeah I agree with what you said, actually I commented on a thread about C# 4, I dont like much the direction is taking with lots of dynamic typing features but C# 3 it is a great language.

Big systems should be coded with static typing languages, not duck typing.

C# 4 is getting one dynamically typed feature, 'dynamic'. This should help C# code to work with IronRuby code, etc. It's also getting contravariance and covariance in its generics, and thankfully didn't copy Java's wildcards when doing so.