3 ms·
You probably know, but F# exists if you want a functional language in the .NET ecosystem. Granted, you end up dealing with a bunch of OOP libraries still since
by kroltan 6y ago
You probably know, but F# exists if you want a functional language in the .NET ecosystem.
Granted, you end up dealing with a bunch of OOP libraries still since .NET is very C#-centered, but the language is pretty good and the integration is painless.
- forest_dweller 6y agoIf I wrote a F# codebase at a lot of companies I would find myself swiftly booted out the door.
- kroltan 6y agoOh yes you'd definitely get booted for using F# in a C# shop. I love F# but would never use it at my current job because nobody else on my team knows anything about FP, even though the language itself can be learned in about a week since it's so simple.
- forest_dweller 6y agoMy comment was a glib comment and wasn't supposed to be taken too seriously.
- kroltan 6y agoFair enough, but it also outlines a bit of truth that you shouldn't necessarily go against the grain of the programming culture of a workplace just due to personal preference.
- elamje 6y agoYes, I’d love to use F#, but not a lot of opportunities out there. And .NET, like you mentioned, is very C# focused which would become frustrating at times.
- jackfoxy 6y agoMy experience with F# over 7 years of production coding is for most needs there is already an F# .NET library or wrapper over an OO library. It's mostly only very specialized needs that drive me to an OO .NET library.