12 ms·

There are plenty of languages built on the CLR [1], including variants of Clojure, Python, and Ruby. Then there's the "official" languages: C#, C++/CLI, VB.NET,

There are plenty of languages built on the CLR [1], including variants of Clojure, Python, and Ruby. Then there's the "official" languages: C#, C++/CLI, VB.NET, JScript.net. I suspect what's going on is that 1) unlike Java C# has actually evolved so the need for "escape hatch" languages is lesser, and 2) .NET developers want to use languages with rich Visual Studio tooling. https://en.m.wikipedia.org/wiki/List_of_CLI_languages https://en.m.wikipedia.org/wiki/List_of_CLI_languages

GordonS 9y ago
Don't forget F#!
- pjmlp 9y ago
  Its future is uncertain with lack of UWP support, the way things are going expect Microsoft to offer it to the community. I hope being proven wrong though.
  - GordonS 9y ago
    With the exception of UWP support (which I'm sure will come), F#'s future seems pretty certain to me. There seems to have been a lot of interest in it lately, probably fueled by the current hype over functional programming.
    - pjmlp 9y ago
      Check the newly released Visual Studio 15.3. https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net-core-roadmap-update/ https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net... Apparently lack of support wasn't enough to delay Visual Studio 15.3's release, just let the community deal with it.
      - GordonS 9y ago
        Point taken; it's obviously not a top priority for them, with C# remaining the primary focus. I guess that makes sense, since so many more devs use C#. While dissapointing, I'm sure (well, I hope :) F# support will land in VS before too long. In the mean-time, VS Code really is a great alternative
      - TensorMetric 9y ago
        It also doesn't help when prominent members of that that community keep spreading FUD about UWP, driving more Windows developers away from F#. https://www.reddit.com/r/programming/comments/6tppt4/f_and_net_core_roadmap_update/ https://www.reddit.com/r/programming/comments/6tppt4/f_and_n... https://twitter.com/k_cieslak/status/896658073338695680 https://twitter.com/k_cieslak/status/896658073338695680 https://twitter.com/k_cieslak/status/896847612766289921 https://twitter.com/k_cieslak/status/896847612766289921 https://twitter.com/k_cieslak/status/897036090489671680 https://twitter.com/k_cieslak/status/897036090489671680
        pjmlp 9y ago
        Fully agree with you regarding that prominent member. Of course he doesn't care about UWP support, as he wants to promote his own VSCode plugin.
        TensorMetric 9y ago
        Also sad to see those members who liked his tweets.
        pjmlp 9y ago
        We can forget about UWP support, it isn't going to happen in the near future, who knows if it ever will. "The F# team is currently focused on .NET Core tooling in Visual Studio and further support for .NET Core as it evolves. There is no ETA for .NET Native/UWP support at this time." -- Phillip Carter [MSFT] https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net-core-roadmap-update/#comments https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net... Better focus on C# and C++ and call it a day.
        TensorMetric 9y ago
        I really can't stand C#. F# is what drove me to .NET in the first place. And I don't like going back to C++, is there any GUI/XAML tooling for it? If not, I'd rather use something like Rust.

GordonS 9y ago

Don't forget F#!

pjmlp 9y ago
Its future is uncertain with lack of UWP support, the way things are going expect Microsoft to offer it to the community. I hope being proven wrong though.
- GordonS 9y ago
  With the exception of UWP support (which I'm sure will come), F#'s future seems pretty certain to me. There seems to have been a lot of interest in it lately, probably fueled by the current hype over functional programming.
  - pjmlp 9y ago
    Check the newly released Visual Studio 15.3. https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net-core-roadmap-update/ https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net... Apparently lack of support wasn't enough to delay Visual Studio 15.3's release, just let the community deal with it.
    - GordonS 9y ago
      Point taken; it's obviously not a top priority for them, with C# remaining the primary focus. I guess that makes sense, since so many more devs use C#. While dissapointing, I'm sure (well, I hope :) F# support will land in VS before too long. In the mean-time, VS Code really is a great alternative
    - TensorMetric 9y ago
      It also doesn't help when prominent members of that that community keep spreading FUD about UWP, driving more Windows developers away from F#. https://www.reddit.com/r/programming/comments/6tppt4/f_and_net_core_roadmap_update/ https://www.reddit.com/r/programming/comments/6tppt4/f_and_n... https://twitter.com/k_cieslak/status/896658073338695680 https://twitter.com/k_cieslak/status/896658073338695680 https://twitter.com/k_cieslak/status/896847612766289921 https://twitter.com/k_cieslak/status/896847612766289921 https://twitter.com/k_cieslak/status/897036090489671680 https://twitter.com/k_cieslak/status/897036090489671680
      - pjmlp 9y ago
        Fully agree with you regarding that prominent member. Of course he doesn't care about UWP support, as he wants to promote his own VSCode plugin.
        TensorMetric 9y ago
        Also sad to see those members who liked his tweets.
        pjmlp 9y ago
        We can forget about UWP support, it isn't going to happen in the near future, who knows if it ever will. "The F# team is currently focused on .NET Core tooling in Visual Studio and further support for .NET Core as it evolves. There is no ETA for .NET Native/UWP support at this time." -- Phillip Carter [MSFT] https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net-core-roadmap-update/#comments https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net... Better focus on C# and C++ and call it a day.
        TensorMetric 9y ago
        I really can't stand C#. F# is what drove me to .NET in the first place. And I don't like going back to C++, is there any GUI/XAML tooling for it? If not, I'd rather use something like Rust.