In all fairness, I haven't touched Visual Studio (for either F# or C# dev) in at least 18 months, so you're probably right.
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.
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.