They've always had this annoying tendency to stray from the things we need them to be working on (getting a 100% feature complete version of the latest .NET CLR) and into things that are cool but not really core, such as the long list described in this post.
I gave them a hard time about this a year ago, when they came up with a similar list of fun side projects yet still had major pieces of .NET 2.0 unfinished, such as this one that was stopping me from using them:
Sounds like they have enough people on the core now that they're mostly up to date on 3.5 and starting on 4.0. That's great news (more-so than this blog entry, but it provides a nice excuse to give them some props).
http://www.mono-project.com/Compatibility
They've always had this annoying tendency to stray from the things we need them to be working on (getting a 100% feature complete version of the latest .NET CLR) and into things that are cool but not really core, such as the long list described in this post.
I gave them a hard time about this a year ago, when they came up with a similar list of fun side projects yet still had major pieces of .NET 2.0 unfinished, such as this one that was stopping me from using them:
https://bugzilla.novell.com/show_bug.cgi?id=346561
Sounds like they have enough people on the core now that they're mostly up to date on 3.5 and starting on 4.0. That's great news (more-so than this blog entry, but it provides a nice excuse to give them some props).