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.
Earlier this week Microsoft Research published a paper outlining a framework for Cloud Computing codenamed Orleans. The framework is intended for cloud computing applications where a client such as a PC, smartphone or embedded device is employed.
Don Syme has announced the release of the F# compiler source code as a code drop under Apache 2.0
In 2009 Microsoft’s Lucas Bolognese announced a commitment to co-evolution for C# and Visual Basic. And the productization of F#, some have assumed it extends to that language as well. But by only offering C# in the initial release of WP7, this promise has been brought into doubt.
Slipped into the Silverlight Tools for Visual Studio release is F# for Silverlight 4. While C# or VB is still recommended for UI design, F# offers some interesting capabilities for the business tier, especially if it is heavy on computations or data processing logic.
Accelerator V2, currently a preview build, is a .NET managed library easing the task of writing data-parallel programs executed on multi-core CPUs and GPUs.
Having a new logo, Visual Studio 2010 Beta 2 made it’s debut yesterday with performance improvements and better stability, setting the stage for the RTM release on March 22, 2010. F# is integrated with Rx, while Azure Tools are in the works.
In this interview Eric Nelson talks about what’s coming in VS 2010, the C# – VB.NET convergence, the introduction of Parallel as a library, and Azure cloud computing.
F# was supposed to free us of the tyranny of the unchecked null. Alas not only does the compiler lack null checking, it introduces several more kinds of null.
Creating wrapper functions for pre-existing stored procedures is surprisingly difficult in .NET. Stored procedures have certain calling conventions that aren’t generally used in the .NET Framework and many of them are not supported at all. For example, C# doesn’t support optional parameters and neither .NET language supports optional parameters on nullable types.