An independent group of developers and companies have joined forces to create the F# Software Foundation. This organization’s goal is to “is to promote, protect, and advance the F# programming language, and to support and facilitate the growth of a diverse and international community of F# programmers.”
Over the last year lots of Type Providers for F# were released for a variety of data sources including AppSettings, Excel, XAML, and the statistical programming language R. And with many of these being offered as open source projects, learning how to create your own has become much easier.
Math.NET recently released numerics library with improved F# including support for Windows Phone 8 and vector slicing.
InfoQ's research initiative continues with an 11th question: "Why Are You Not Using Functional Languages?". This is a new service we hope will provide you with up-to-date & bias-free community-based insight into trends & behaviors that affect enterprise software development. Unlike traditional vendor/analyst-based research, our research is based on answers provided by YOU.
Microsoft Research has published a white paper explaining how Type Providers makes F# useful for accessing and processing “internet scale” information sources.
Microsoft released two new editions of its free Visual Studio Express 2012 series that will target F# and traditional Windows desktop applications. This enables developers using C#, C++, F#, and Visual Basic .NET to take advantage of VS2012's improvements.
The upcoming release of .NET Framework 4.5 brings in several new features for F# 3.0 (F Sharp) language such as a new type attribute, triple-quoted string literals, auto-properties, and unused variable warnings in addition to the core features such as type providers and LINQ queries.
F# 3.0, included in the Visual Studio 11 beta, gains the ability to use LINQ expressions. Other features include support for Portable Libraries and auto-implemented properties.
F# is emerging as a great choice for Numerical computing. Reasons? Functional design, libraries such as PowerPack, MathProvider and Math.NET and the interoperability of the .NET Framework.
Microsoft recently announced a developer preview release of F# 3.0 – new features include LINQ-support through Query expressions and a Type Provider System along with a set of built-in providers that allow succinct programming against a variety of data sources.
The new Async CPT for VB and C# looks like it may actually make it into the core language. But with all the emphasis on multi-core systems, why is Microsoft investing so heavily in syntax for designed specifically for making single-threaded asynchronous programming easier?
Last month Vladimir Kelman asked if it were possible to use F# with the new Razor view engine. After talking with Scott Guthrie and Marcin Dobosz we learned that it is possible, if you want to put in the effort to build all necessary plugins yourself.
MonoDevelop has become the third IDE to support Microsoft’s F# language. With .NET support essentially dead on the Eclipse IDE and WebMatrix being targeted for causal developers, it is likely to be the last IDE to add support for it in the foreseeable future.
Last week Miguel de Icaza published a long post listing all the work the Mono team at Novell has been doing since the move to GitHub in July 2010. Much of the new work has been around language development and MonoDevelop improvements.