4 ms·
That sounds exactly the same as F# (except there might be more jobs in scala). F# is on .NET CLR and you can use all the .NET libraries, and it lets you fall b
by Dayshine 7y ago
That sounds exactly the same as F# (except there might be more jobs in scala).
F# is on .NET CLR and you can use all the .NET libraries, and it lets you fall back to an imperative style if you need to!
- pjmlp 7y agoTry to use EF, WCF, UWP, WPF from F#.
- deleted 7y ago[deleted]
- McWobbleston 7y agoEF isn't really needed with Dapper and the available SQL type providers. Even still it's totally naturally to have a C# project holding the base EF stuff which you reference from your F# projects
- pjmlp 7y agoTry to use that argument to sell F# to the large majority of .NET shops.
- thrower123 7y agoThe vast majority of .Net shops would run shrieking when faced with F# code. I still run into people regularly that shun the var keyword for type inference in C# because they think it is actually the evil old VB6 Variant type.
- pjmlp 7y agoYep that was kind of my point.
- Iwan-Zotow 7y ago> you can use all the .NET libraries did you try it? Hint: there is a lot of things required before F# could use latest WinUI or WPF
- svick 7y agoI wouldn't call those libraries. If you have something that's actually just a library, using it from F# should not be a problem.