3 ms·

Microsoft explained why we love Rust so much ;)

• DeathArrow 2y ago
  Except F# is far more pleasant to use than Rust.
  • akkad33 2y ago
    Is it? There is a lot of uphill battle on using DotNet librairies that are mainly developed with C# in mind. So all the nice things about F# like currying, no nulls etc go out the door because you're interacting with C# code. Rust is a first class citizen in its own ecosystem, so you never have to compromise on the strictness of your codebase
    • neonsunset 2y ago
      In practical terms it's mostly source-generators-based functionality and nullability that are an issue. F# 9 gains the ability to transparently understand nullable annotations emitted in C# by Roslyn and expresses them as `T | null` unions, or just as T if the T is non-nullable. Currying and other F#-specific features are simply syntax, there is no inherent limitation for defining a simple curried expression that ends up calling into a method implemented in a different .NET language. The bigger issues are non-technical where it's just very few companies use F# in production. As for the technical ones - there are not that many and most of them are known (like mentioned above - code generation related, so the criticism usually mentions the same limited set every time, like code-first model definition in EF Core).