4 ms·

I feel that. It always seems to come down to tooling; the moment you have to fight with tooling for a language, it immediately adds friction. Sure, individual d

I feel that. It always seems to come down to tooling; the moment you have to fight with tooling for a language, it immediately adds friction. Sure, individual developers can overcome these problems, but it still decreases the adoption rate of said language. It makes me wonder what differed between the .NET and JVM runtimes, with .NET moving towards fewer languages, whereas the JVM supports more.

pjmlp 5y ago
Microsoft seems to have some issues keeping their teams running, the Common Language Runtime has turned into C# Language Runtime, as VB doesn't get feature parity with C#, F# is only considered for writing libraries, and C++/CLI is kept alive thanks to WPD and some key partners. Meanwhile on the native side C++/CX gets killed and replaced with C++/WinRT, lacking VS tooling and no roadmap to when it will ever get it. It is already 5 years old. .NET Native is stuck in C# 7 and VB 15, without any clear road if it will ever be updated. Project Reunion started one year ago as the big reunification of Win32 and UWP application models, and what we got was a tiny 0.5 release, where lots of stuff is missing, not clear roadmap on the UWP transition, Xbox and HoloLens support, VS XAML designers are planned only for 2022, if we get lucky and the project doesn't get ramped down. Just check some of the repos on GitHub and the endless amount of open issues. Sometimes I wonder what is everyone actually doing.