Why over Haskell? * Easy multi-platform targetting and platform bindings without fuss. * Mature and supported BCL and 3rd party libraries * Access to the .NE

Why over Haskell? * Easy multi-platform targetting and platform bindings without fuss. * Mature and supported BCL and 3rd party libraries * Access to the .NET ecosystem tooling like profilers, debuggers etc * Easy to use Native FFI without having to write boilerplate C stubs * more predictable reasoning about performance because of strictness by default. * Built-in Units of measure without perf cost. * Type Providers allowing typed access to untyped data and much more [F# 3.0: Data, Services, Web, Cloud... at Your Fingertips] (http://channel9.msdn.com/Events/TechEd/Europe/2012/DEV338 http://channel9.msdn.com/Events/TechEd/Europe/2012/DEV338) http://www.navision-blog.de/2012/03/25/typed-access-to-json-and-xml http://www.navision-blog.de/2012/03/25/typed-access-to-json-... http://www.navision-blog.de/2012/03/22/wpf-designer-for-f/ http://www.navision-blog.de/2012/03/22/wpf-designer-for-f/ http://blogs.msdn.com/b/dsyme/archive/2012/08/03/access-statistical-packages-from-r-with-f-3-0.aspx http://blogs.msdn.com/b/dsyme/archive/2012/08/03/access-stat... * Built-in support for runtime code quoations, with code inspection * Built-in support for runtime reflection * Subtyping without greenspunning around. * Easier to fallback to imperative code. * Extensible computation expression syntax for more than just monads.