Hi Jay I apologize if I did make it sound like that, my intention was to communicate what we talked about in a previous episode (the announcement of Mono 2.0) where it was made clear from the release notes that while the C# compiler has (I believe) all language features for .NET C# 3.0, most of the libraries are still at 2.0 with some 3.0 features, and in particular the LINQ implementation is limited to XML only at present and not to any kind of database persistence option. This is also about a year behind the availability of .NET 3.5 and LINQ. This is impressive progress for an open source project, but it is also not something I would base a business decision on.
I use Linux every day and re-evaluate Mono frequently as an alternative to .NET, and my test is based on being able to take a non- trivial .NET application and run it on Mono. This might be unfair, but it is the same criteria for using Java across platforms (compatibility issues in Java tend to be related to poor use of file paths and other incredibly simple fixes like that). I hear Casper's argument a lot, but realistically I don't know of many companies selecting just Mono for all platforms, and the compatibility isn't strong enough from .NET to Mono still (witness the fact that I still can't use silverlight applets on my linux box - and I would because the NetFlix streaming on my linux box would be very useful indeed). In a nutshell, my concerns over Mono are the same as they always have been. Compatibility is both the language and the library features. LINQ working on RDBMSs would be a huge jump forward, but even then can I take a .NET 3.5 C# application and run it on Linux with minimal changes? Java's big advantage, the same that it has always had, is that this does work, on all the platforms I use, and languages like Scala, Groovy, Jython, JRuby etc. all build on that advantage. I should also point out that I use and like Banshee and f-spot on Linux - they are great applications and very well written/constructed. Notably though, I have yet to see flagship applications like this running on Mac or Windows... Cheers Dick On Nov 22, 7:11 pm, "Jay R. Wren" <[EMAIL PROTECTED]> wrote: > While Mono just released 2.0 and is scheduled to release 2.2 on > December 8th, these version numbers do not correspond to ANY numbers > as used by Microsoft for .NET. > > Mono 2.0 shipped with full, 100%, compatibility with C# 3.0. We have > lambda, LINQ, extension methods, automatic properties and everything. > > At around 24minutes Dick made it sound like this was not true. > > Mono is a very real alternative to Java. I know you guys seem to love > JVM, but... its just a VM. I'd love it too if I could write C# and > target it. > > As for addition of dynamic, all I can say is that if you don't like > it, don't use it. :) > > Thanks for the show. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
