Username or EmailPassword
I agree completely about the technical merits of .net/mono, and how nessicary it is that we get a managed language as a core platform for gnome.
Where i disagree starts here
"And yes, while Java is a very consistent development environment, it is not usable for such a task. GCJ exists with a lot of ambition and GCC is in unmanaged (GCJ has a GC) world is what .NET is in managed. It is a good move from mono's side to support java. And I hope that they will do that good. "
Java as a platform is far more mature and complete, it will take .net years to get to the point that java is at already. There is huge amounts of open java development out there already (check out the jakarta project, or spend some time on sf.net), java is made by a company that is far more open source friendly, and doesnt have a long history of dirty pool that microsoft is famous for.
The big problem with desktop java isnt even java, its swing. Swing, while being a fantastic toolkit, is insanely easy to misuse. What you get is an extremely unresponsive and ugly application. But if java were the new gnome platform, we wouldnt be talking swing, we would be talking something like Java-Gnome, the GTK bindings for java, in which case you would expect the same responsivness as a Gtk# app. If you dont believe me, look for benchmarks. The argument isnt weather java is slow or not, its weather its faster then something natively compiled in C.
Last but not least, java is a managed language. So is python. It would make far more sense for gnome to embrace the two of those as the new api of the future then go for mono, which is a baby by comparison.