This includes links to some key frameworks plus a link to the F# Software Foundation guide to F# web development for more comprehensive community listings
3. The front page also features "F# for machine learning". This page features a few resources (please add more!) and again links to the @fsharporg pages for comprehensive community listings (you can add more material there too). docs.microsoft.com/dotnet/fsharp/…
4. The front page also features "Deploying and Managing Azure Resources" and links to Farmer, the community-developed tool for using F# for this docs.microsoft.com/dotnet/fsharp/…
5. We now have a dedicated page for using Apache Spark with F# on Azure
6. We now have thin link-based pages under "F# tooling" (previously only had one entry, despite so many tools being available for F#!). This includes a page on .NET Interactive notebooks docs.microsoft.com/dotnet/fsharp/… and F# dev tools docs.microsoft.com/dotnet/fsharp/…. Please add more
8. For people wanting an overview of the F# language, this is the landing page for the F# language guide, it's now well organized. You can glance through it quickly to confirm that you know the principle areas of the language and find what you need
10. Functional programming has been de-emphasized in the learning sequence - the "succinct, robust and performant" properties of F# are emphasized that align and FP emerges as a practical technique, rather than being something you need to learn before you start to code
A farewell to Simon Peyton Jones as he leaves Microsoft Research
Subject: RE: New horizon
I would like to add a few words to what Chris has written. I know I am also speaking for Mads, the current lead designer of C# (cc’d)
From 1997 to 2015, Simon PJ was pivotal in the Programming Principles and Tools group at MSR Cambridge. The work of that group included major contributions to the research and practice of programming, a stream of seminal publications,..
... and succeeded in changing the conceptual foundation of programming for millions of programmers through direct contributions to Haskell, C# and F# - and transitively through profound influence on other languages.
One simple way to help F# is to help us fill in basic F# code samples for all the F# core library functions. These should have been done long ago, but let's do them now!
@chaldal.com is a global company centred in Dhaka, Bangladesh. You can read more about them on their website.
I've long believed F# could have a strong role in up-tooling the software skills of developing nations, giving them a competitive advantage.
But for me, this one is also very personal.
In 1993 I had the opportunity to travel to Bangladesh, to visit my brother, who was working doing flood modelling on the internationally sponsored Flood Action Program.
"All our new code is in F#, we started off from a C# codebase, so that made the transition somewhat manageable, as new F# code can be directly called from C#, and vice versa (still took over 2 years)..."
".... All new frontend apps are also being written in F# (using Fable), as of 6 months back, migrating away from TypeScript, this forces everyone into a "design your model first, and well" paradigm...."
It's really strange what nonsense people put up with in C#.
This business where expression results are implicitly discarded from statements is just insane in the 21st century. So much information loss just waiting to happen without even a warning.
Other gaping holes in the C# design I've noticed this last week:
- no way to implement interfaces or abstract classes using an expression, meaning stupid extra classes
- no implicit construction for classes (to give another form of closure capture for object imlpementations)
- no expression form for generative list or sequence expressions (making HTML DSLs a mess among other things)
If mass wearing of masks make just 0.01 shift in the spread per day, from say 1.22x to 1.21x, there would now be ~20% fewer cases (and ~20% fewer deaths) in the UK since March 12.
I had to double check that multiple times.
This sort of result should have been hammered into our collective consciousness throughout February and early March. Every little effective intervention, widely adopted, saves many, many lives.
The thing is, that 0.01 difference accrues every single day, afresh - and slightly compounded too. Every day we do a small, effective intervention, we accrue it's life saving effect all over again. Every single day. All over again.