kowalgta

11 ms·

1. 1.▲
   by kowalgta 1y ago

   I've worked with .net professionally for almost 20 years. At the beginning with C# while last decade almost exclusively with F#. F# is just a better language. Simpler, more concise, more readable with stronger type safety. I will never
2. 2.▲
   by kowalgta 6y ago

   Usage of C# packages from F# is simple and without issues. The other way is a bit more clunky, but frankly, you will not want to write any C# once you are on the F# side. I have been programming in F# full time for the past 7 years and I ho
3. 3.▲
   by kowalgta 6y ago

   As others mentioned - using smart constructor technique, but not directly as F# has no dependend type capability. Smart constructor technique works well with 'parse, don't validate' approach [0]. You can push type constructio
4. 4.▲
   by kowalgta 6y ago

   We use F# to build fairly complex portfolio management apps. It's a great match for F# to Javascript transpilers (Fable, WebSharper). It makes it easy to share functions and types between UI and backend and to have powerful type safety