|
|
|
|
|
|
by GiorgioG
1983 days ago
|
|
|
What killed F# was Microsoft never putting enough internal resources on it. It's been consistently an afterthought in various releases of VS, initial .NET Core support, etc. As a C#/.NET Dev for 20 years, I've tried several a few times to use F# only to find broken tooling, lousy IDE support in VS (compared to C#, etc.) Jetbrains Rider supposedly has better F# support, but given Microsoft's lack of interest and a tiny community, I still can't be bothered to pick it up. I'm more likely to learn/use Elixir than F# at this point. |
|
|