Did you know there was more to the type matching operator than just pattern matching and exception handling?
One thing I never really thought about a great deal before was the term ‘on-line’ friends and what it might or might not mean. I mean what does that really mean? Are they just actual friends or just “on-line” friends?
After enjoying owning a 150mm refractor telescope for a year, I decided I wanted to upgrade.
So this is my Christmas special. I’ve been asked on numerous times to write about the F# addin for Xamarin studio which is in the fsharpbinding repo, this repo is shared with the emacs support and also the Sublime Text support. So in this edition we will be taking a deep dive into the terrifying deep depths of the F# compiler and F# addin development…
While I was visiting Boston earlier in the year I had the misfortune of kicking myself in the teeth with reflection. It’s something all programmers inevitably go through with reflection API’s as they are inherently untyped, a simple typo can leave you tearing out your hair or punching through your monitor! Yeah there’s things the horizon that will help namely the nameof expression in C#6 which should help in some areas, that’s if your willing to pay the price of using C#, but I wont go into that here :–). In F# we can leverage Type Providers fairly easily to wrap API usages in cases that we are interested in, or even create a general usage with a little more effort.
First of all the title, redux because I’m revising post I started on earlier in the year, compression because this has to do with compression, and Flux, which is also part of the redux, one of the first things I remember writing on the net was an article about Flux Compression Generators on H2G2, its still there too!
Wow its been a long time since I wrote anything!
For those of you visiting here may be pleased to know that I’m finally getting round to writing again, but before a post with any real content I just wanted to mention a few things.
For any of you that are aware of the newly updated Xamarin Web site, you may have seen the following:
Objective-C was ahead of its time 30 years ago. C# is ahead of its time today. Anything you can do in Objective-C or Java, you can do in C# with Xamarin—usually more succinctly and with fewer bugs.
What is also true is that F# is way ahead of its time, and you can produce even more succinct code with even fewer bugs than C#!
With the release of Xamarin 3 we have a swathe of new features to the platform, but obviously the most important one is obviously F# support is now included by default in Xamarin Studio so there is no escape from the awesomeness of F#!
So what else have we got, well loads of other goodies too like Xamarin Designer for iOS, Xamarin.Forms, Major IDE enhancements, Improved code sharing with PCL and Shared projects, and BCL Documentation. You can see the release blog post here: announcing Xamarin 3
There are tons of things I could show you, but for this post lets have a quick look at Xamarin.Forms
After choosing to not surf the seas of Twitter, am I any less current in the world of F#, did I miss anything important that a real-time stream would of alerted me to?