With these kind of remarks, the point being that .NET team isn't serious enough for having cross-platform GUI tooling that would enable a proper cross-platform version of Visual Studio.
Visual Studio for Mac (nee Mono Develop), could have been it, instead they decided to kill it, and focus on VSCode, which has already been communicated a couple of times, C# Dev Kit will never cover all use cases of VS proper, and it is also under the same license anyway.
So MAUI will never support GNU/Linux, was also not used in VS4Mac due to its Catalist underpinnings, Forms and WPF will stay Windows forever, MS will never used Uno or Avalonia, thus it leaves a Java IDE platform and Electron for their cross-platform tooling.
All, because regardless of what the .NET team does, upper management still wants to use .NET to drive Visual Studio and Windows licenses.
Visual Studio for Mac (nee Mono Develop), could have been it, instead they decided to kill it, and focus on VSCode, which has already been communicated a couple of times, C# Dev Kit will never cover all use cases of VS proper, and it is also under the same license anyway.
So MAUI will never support GNU/Linux, was also not used in VS4Mac due to its Catalist underpinnings, Forms and WPF will stay Windows forever, MS will never used Uno or Avalonia, thus it leaves a Java IDE platform and Electron for their cross-platform tooling.
All, because regardless of what the .NET team does, upper management still wants to use .NET to drive Visual Studio and Windows licenses.