F# 4.0 has been released for the big three major platforms (Windows, Mac OS X, and Linux). F# 4.0 brings a host of new features, bug fixes, and performance improvements that benefit users of the language whether or not they are writing code in Visual Studio 2015.
Two more significant bugs have been found when using RyuJIT and .NET 4.6. Code recompilation is not necessary to experience the effects, merely running existing code on RyuJIT (which ships in .NET 4.6 and is enabled by default) will cause severe problems.
While all of the recent news has been focused on C# and Windows 10, F# isn’t standing still. Along with Visual Studio 2015 RC is the latest version of F# 4.0.
Microsoft is continuing their move from CodePlex to GitHub for their open source offerings. The F# compiler was moved on the 13th, with the Roslyn based C# and VB compilers following a few days later.
Microsoft announced a pre-release of F# 4.0 for Visual Studio 2015 Preview which can be installed through a Visual Studio update package. The update brings improvements to language and tooling features that can positively impact developers' daily life, several commenters said.
The Xamarin Evolve 2014 event taking place these days in Atlanta, US, has produced a number of news related to the cross-platform tools Xamarin makes: Android Player – a hardware accelerated Android simulator-, Sketches –a REPL-like environment-, and Profiler –a C# code profiler-.
The ASP.NET vNext runtime uses the Rosylyn compiler to compile and load the C# sources before running them. David Fowler shows how you can leverage the DI-by-design approach of KRuntime to inject support for your own language.
F# has supported both iOS and Android native programming through Xamarin since at least Xamarin 4.8 and can be efficiently used to create native apps on both platforms. Let's give a look at some experience reports.
A focus on behaviour and a more declarative style of code are two benefits for Domain-Driven Design (DDD) when moving from an object-oriented language like C# to a functional one like F#, Lev Gorodinski claims in a recent presentation, using an example that includes event sourcing and Command-Query Responsibility Separation (CQRS) to show some of the benefits and challenges in a move to F#.
Using a functional language in domain-driven design (DDD) the actual code can often become simple enough to be used instead of UML diagrams when discussing with domain experts, Scott Wlaschin stated in a recent talk about domain modelling together with functional programming using F#.
Visual F# Tools 3.1.1 has been released with support for both desktop and web versions of Visual Studio 2013 Express edition in addition to the ability to install it directly from PowerShell prompt.
F#, Microsoft's powerful functional language, is receiving several improvements that refine the language in several ways: .NET 4.5 + Windows Store portable library support, project round-tripping, and several language enhancements including named union type fields, and extensions to array slicing.
FunScript is an F# compiler library enabling developers to write single-page web applications in F# and running them in the browser or on the server via Node.js.
The usage of Microsoft F# in conjunction with QuantLib provides extensive possibilities for developers to build quantitative financial applications and this news report examines the steps required to create a simple F# application with QuantLib.
Sometimes the best way to understand pitfalls in one language is to see how another language prevents them. Tomas Petricek, author of Real-World Functional Programming, discusses seven common mistakes found in asynchronous C# code and demonstrates how F# makes them less likely to occur.