(no title)
avinium | 6 years ago
I'd say the future looks pretty bright for F#. It's really resonating with an audience that wants "functional where I want, but practical where I need".
avinium | 6 years ago
I'd say the future looks pretty bright for F#. It's really resonating with an audience that wants "functional where I want, but practical where I need".
snagglegaggle|6 years ago
narimiran|6 years ago
Last time I tried, I couldn't get FSI working on Linux without Mono. Did something change recently?
avinium|6 years ago
pjmlp|6 years ago
avinium|6 years ago
That being said, UI isn't a strength on .NET to begin with, so I think it's unfair to point that criticism at F#. Uno seems to doing some great things though.
The F# SQL type provider, however, is great. For those who don't know, this generates design- and compile-time types based on your (live) DB schema, enabling auto-complete and compile-time type checking for SQL queries. I do agree that Ionide/VS Code support isn't quite there yet.
To be perfectly honest, I don't know what you're referring to by "application architecture design".
It's definitely not perfect - I never claimed otherwise. I'm just saying that everything points to MS increasing support for F#, not the opposite.