Non-microsoft languages commentary

Question

I develop radar applications on Linux and I have been watching .NET for 20 years.
I was excited to see the goals for .NET 5.0 and I thought it might be the time to
move to .NET. But, I was disappointed to see that the goal was just interoperability
with Java and Objective C/Swift. The concept of .NET is a significant improvement
over Java and I can see some potential features that could be added for high data rate
radar applications. But, until .NET finds a way to truly support multiple languages that are not
Microsoft languages as .NET languages, it is just a Java clone that may or may not have some
minor improvements over Java. For radar applications, adding something like Octave.NET would
make a lot of sense. Being truly cross platform and cross language offers significant performance
and portability advantages for distributed web and non-web applications. For us, our first step would have
been to migrate a significant Java application to .NET, but that doesn't appear to be a very reasonable thing
to do at this point.

Answer 1

Microsoft only has the resources on some of the core components and serves its primary customer base,

• .NET Core runtime
• C#/F# languages (VB.NET is phasing out, J# is dropped a few years ago)
• Frameworks like ASP.NET Core, WinForms, WPF, Blazor, and EF Core

It would be the responsibilities of third parties to fill the gaps and serve special needs like yours, and companies like RemObjects do enable Java applications to migrate to .NET runtime,

https://www.elementscompiler.com/elements/iodine/

Answer 2

Thanks for your answer.

I understand Microsoft's position, but it is hindering the adoption of .NET for non-Windows platforms ... which also limits the use of Microsoft languages
on those platforms ....

mono had ikvm and ikvmc which appear to be supported by a third party now .... disappointing that this wasn't kept with NET 5.0 or NET ??

I hope I can find an open source alternative for Java. This is my first requirement for moving to .NET.
After the move, if it happens, some of the features we would like to add to .NET would probably be prototyped in C#.