3 ms·

Hey Philip, great post - really informative. Especially happy to see that the nightly releases are coming along considering the pace of improvements by the like

by saulr 10y ago

Hey Philip, great post - really informative. Especially happy to see that the nightly releases are coming along considering the pace of improvements by the likes of Vasily and all the rest. I do have a small question about the Visual F# team at Microsoft. Are there any plans to grow the team at all? It seems that the company deems F# as a second class .Net language, preferring VB.Net/C# when it comes to contributions from employees and IDE features. Given the popularity of F# in surveys such as the recent annual Stack Overflow developers survey, is there any interest at the company to put more manpower to F# development? P.S. I hope to see you around at the F# Exchange in London next month if I go.

danielvf 10y ago
Microsoft's language roadmap list F# as their third most important language: https://blogs.msdn.microsoft.com/dotnet/2017/02/01/the-net-language-strategy/ https://blogs.msdn.microsoft.com/dotnet/2017/02/01/the-net-l... But I wouldn't judge too much based on team size - the Visual Studio Code team is very small, and yet has an incredible velocity and quality.
- willtim 10y ago
  I saw a demo of VS code today, as a Haskell IDE. I was very impressed with what I saw.
phillipcarter 10y ago
Here's what I'll say: By sitting the F# language service atop Roslyn Workspaces, F# in Visual Studio is in a far better place infrastructure-wise than it has ever been. Roslyn Workspaces are the lower-level piece that nearly every bit of .NET IDE work is done in. A great example of how that enables F# in other areas is how the idea of support for the Roslyn Project System[0] went from a complete unknown to a reality. The work needed to support F# in various areas went down by orders of magnitude as a result of this work. [0]: https://github.com/dotnet/roslyn-project-system/pull/1670 https://github.com/dotnet/roslyn-project-system/pull/1670 P.S. I'll be in London for a week. Even if you can't make F# Exchange, I'd love to meet up for coffee, beer, or whatever!

by saulr 10y ago

danielvf 10y ago

Microsoft's language roadmap list F# as their third most important language: https://blogs.msdn.microsoft.com/dotnet/2017/02/01/the-net-language-strategy/ https://blogs.msdn.microsoft.com/dotnet/2017/02/01/the-net-l... But I wouldn't judge too much based on team size - the Visual Studio Code team is very small, and yet has an incredible velocity and quality.

willtim 10y ago
I saw a demo of VS code today, as a Haskell IDE. I was very impressed with what I saw.

phillipcarter 10y ago

Here's what I'll say: By sitting the F# language service atop Roslyn Workspaces, F# in Visual Studio is in a far better place infrastructure-wise than it has ever been. Roslyn Workspaces are the lower-level piece that nearly every bit of .NET IDE work is done in. A great example of how that enables F# in other areas is how the idea of support for the Roslyn Project System[0] went from a complete unknown to a reality. The work needed to support F# in various areas went down by orders of magnitude as a result of this work. [0]: https://github.com/dotnet/roslyn-project-system/pull/1670 https://github.com/dotnet/roslyn-project-system/pull/1670 P.S. I'll be in London for a week. Even if you can't make F# Exchange, I'd love to meet up for coffee, beer, or whatever!