You are right if talking about the efforts improving C# and CLR, taking the lessons out of Midori, Blazor and Aspire.
Regarding F#, VB, and C++/CLI, the poor souls are on a lifeline that makes CLR nowadays stand out for C# Language Runtime, instead of the original Common.
And the chaos that reigns on Windows Forms, WPF, WinUI, MAUI certainly isn't helping.
Finally they are constrained in what they can put into C# DevKit as means to not canibalize Visual Studio and Windows sales, it can only be good enough, not great and feature parity.
Also regardless of the reasoning behind it, having TypeScript rewriten into C# instead of Go would have been a great opportunity to make C# more relevant outside Microsoft shops, instead anyone looking to contribute to TypeScript compiler will be learning Go instead.
You are right if talking about the efforts improving C# and CLR, taking the lessons out of Midori, Blazor and Aspire.
Regarding F#, VB, and C++/CLI, the poor souls are on a lifeline that makes CLR nowadays stand out for C# Language Runtime, instead of the original Common.
And the chaos that reigns on Windows Forms, WPF, WinUI, MAUI certainly isn't helping.
Finally they are constrained in what they can put into C# DevKit as means to not canibalize Visual Studio and Windows sales, it can only be good enough, not great and feature parity.
Also regardless of the reasoning behind it, having TypeScript rewriten into C# instead of Go would have been a great opportunity to make C# more relevant outside Microsoft shops, instead anyone looking to contribute to TypeScript compiler will be learning Go instead.