Semantic versioning can be misleading. While F# 4.1 is backwards compatible with F# 4.0, it is by no means a minor release. With both Microsoft and the larger community contributing, several more features were introduced since the F# 4.1 preview in the areas of performance, interoperability, and convenience.
A lot happened in the last year in the .NET ecosystem. Putting aside the details, the bigger picture is difficult to grasp. There is movement in all aspects: cross-platform, cloud, mobile, web apps and universal apps. Developers wonder where all of this is going to lead and what will be required to get there.
In April, for the second time, fsharpWorks organized the F# community survey. Over 600 developers completed the survey in 2016 (which is 15% more than in 2015). The survey provides an insight into the brains of the F# community. In this article, I'll summarize some of the results.
F# Deep Dives is a new book aimed at showing the business value that using F# brings in practice. It presents 11 industrial scenarios and their solution with F# using a functional-first approach.
Type Providers are an essential element for F#’s extensibility model. Dave Fancher shows how to take the tedium out authoring Type Providers using some simple inline factory methods.
The book of F#, authored by Dave Fancher examines the concepts associated with F# with the help of comprehensive explanation and relevant source codes. 1
Adam Granicz shows how the functional programming language F#, along with WebSharper, can be used to tame mobile development. 1
Robert Pickering continues the conversation in this third article on F# and this time focuses on Asynchronous Workflows and the resulting peformance gains obtained when used.
Next in a series of articles on F#, Robert Pickering progresses the discussion to a deep dive on workflows which are the building blocks for creating DSLs. 1
Since Robert Pickering published Foundations of F# in May, the language has grown significantly. We asked him discuss what's new in F#.