I use F# every day, both in my open source and professional work. Love seeing the language continue to improve without going off the rails! I'm looking forward to using the "and!" computations in this release in particular (though I swear they'd already been released).
Edit: oh this post is from November! That's why I thought I'd read about those computations before.
I use OCaml, occasionally, especially for data/transpiler work. I've always wanted to try F#, but it being .NET sort of scares me away. I've always sort of admired the pragmatic beauty of the OCaml ecosystem--at least as much as one can call an ML-derivative 'pragmatic'--though I don't get that same feeling from F#.
Task expressions look neat though, and might give me a reason to try.
I got into OCaml for a while, which naturally led me to try F#. What pushed me away back then was that the tooling lagged behind C#, especially in VS Code, and the C#/F# interop wasn’t as ergonomic as I expected. I liked the idea of using F# for the core and C# around the edges, but it didn’t feel smooth in practice. This was years ago, so maybe the tooling has improved since.
I’ve always wondered whether tighter integration with C# would have led to broader adoption, though that might have changed the character of the language.
4 comments
[ 2.8 ms ] story [ 20.4 ms ] threadEdit: oh this post is from November! That's why I thought I'd read about those computations before.
Task expressions look neat though, and might give me a reason to try.
I’ve always wondered whether tighter integration with C# would have led to broader adoption, though that might have changed the character of the language.