The future of .NET lies in Mono. The future of F# lies in MonoDevelop.

It’s been a year since I last wrote about F# and Mono - what’s happened since then?

F# 3.0 has recently been released, bundled with the new all-grey, ALL-CAPS Visual Studio 2012. The biggest new feature is type providers, bringing some of the benefits of dynamic languages into the type-safe world. Innovations like type providers deserve more industry attention. I really hope these ideas will spread and hopefully languages like Scala will pick them up so more developers (including me) can enjoy the benefits.

OK, that’s cool, but how is good old F# doing? Well, about the same. It lumbers on in obscurity under the massive shadow of Microsoft and whatever crazy idea the company is currently peddling (Win8 metro UI, touch-screen laptops, WinRT, $100 surface covers, pretending Silverlight never happened, etc…) F# is still awesome and deserves a lot more attention and adoption.

Take a look at ThoughWorks latest Tech Radar. F# distant relatives (as in fairly new functional-first languages) Scala and Clojure are steaming ahead and have both reached “Adopt” status. F# is stuck in “assess” never-land. I don’t see many signs of that changing anytime soon.

Take a look at ThoughWorks latest Tech Radar. F# distant relatives (as in fairly new “functional-first” languages) Scala and Clojure are steaming ahead and have both reached “Adopt” status. F# is stuck in “assess” never-land. I don’t see many signs of that changing anytime soon.

F# has limited credibility because of Microsoft. Even though F# is actually open source, it has a very small open-source community. The development is completely driven by Microsoft, and there is very little “open-source buzz” about it, typical for any Microsoft products. F# moves with the same slow cadence as Visual Studio, which in software terms means eons between releases. Any big and open F# frameworks are sorely lacking.

On messaging: firstly, there is total confusion about .NET. Where is it going? Windows 8 is all about HTML5. Anders is doing TypeScript now, Silverlight is dead. There are a lot of frustrated .NET developers out there. I’ve predicted that Mono is the future home and legacy for .NET, and it looks more likely every day. As a die-hard MSDN developer, you might frown upon this fact, but really it’s not a bad thing. Open source and Mono have a lot to offer, for instance, OS independence. This is absolutely critical to continue to drive adoption.

Secondly, F# has always been the odd one out in the .NET space (compared to headline technologies such as C#, VB, ASP). If Microsoft’s messaging on the future of .NET is confusing, their messaging on what F# is and is supposed to be used for is crazy: “Use C# for everything, and if you’re an academic doing data analysis, check out F#.” Screw that - F# is superior to C# in every single way, for any application. Microsoft should promote the hell out of it and stop pussyfooting around. However, I have very little faith that this will ever improve, and F# is (and always has been) dancing close to the edge of oblivion.

There is a big F# shaped hole in the language space currently, on the JVM and elsewhere. Like I stated a year ago, if F# did run on the JVM the story would be completely different, it would have massive adoption. It is a perfect candidate for “the static typed language of choice” in your language toolbox. Today people are seriously looking into Haskell when they get fed up with their gnarly python/ruby projects. Sadly F# is getting overlooked.

So what about Mono and open source then? Don Syme spoke at the recent MonkeySpace conference, and generated a lot of buzz. .NET has never been sexy technology in the hands of Microsoft, but the Xamarin guys are turning Mono into just that. MonoTouch, MonoGame, Unity are some really good products. Mr Don Syme, this is where you and your language belong, this is how you take F# to the next level. Forget about all the in-fighting and bickering at Microsoft and focus on what’s good for F#. That is to embrace Mono fully, it’s your number one platform.

The culture shift for developers who’s been living inside the Microsoft/MSDN bubble moving to Mono is drastic. Mono is an all-out open source community with all it’s up and downsides. Say goodbye to stable, supported releases every 3/4 years and hello to nightly builds and pull requests. That certainly won’t fit all current .NET developers, like lemmings they’ll just move along to whatever Microsoft is feeding them next. Could that be the native renaissance perhaps? :) Real .NET enthusiast should free themselves from the Microsoft shackles and embrace Mono, they’d be much better for it. Join the community, contribute improvements to the garbage collector. Go to awesome conferences in Boston, have fun!

To summarize: how do we save this gem of a language? F# must break out of the Microsoft prison. Ideally, I’d like to see a couple of key members of the team leave Microsoft, get some funding, and set up an independent F# foundation (or maybe join Xamarin). This foundation could pursue important issues like sponsoring key libraries such as web frameworks, making sure the F# MonoDevelop integration is top-notch, etc. So while Microsoft is committing corporate suicide with Windows 8, the .NET and F# community needs to move on.

The future of .NET lies in Mono. The future of F# lies in MonoDevelop.