Comment by sixothree
2 days ago
My guess is portability, then obviously performance.
edit: actually there is a specific answer for this particular project - "We had to rewrite the project in C# to add automated code generation (java doesn't have the goto keyword, making automated ASM translation challenging)". There you are.
I mean, that's more or less the reason why it isn't Java, not why it's ultimately C#. My guess is that Java is just what they're most comfortable with, with C# being similar enough but avoiding specific limitations in that case.
Wasn't C# essentially microsoft throwing their hat in the ring against Oracle and to show off how cool this .net stuff is?
I dabbled in both at around the same time a long time ago for console apps and visual studio's autocomplete / assist / library fetch etc made it easier than Java to get working in but...
Its been so long I forget the origin stories sometimes.
.NET began its life as Microsoft's Java (the platform) along with C# being a mix between Java, C++, and Pascal.
Considering the timing (early 2000s), one can't help but think that it was in response to the legal actions from Sun Microsystems over their usage of the JVM in Windows.
"OK, I'll make my own Java language, with properties and an integrated DSL for queries!"
I think my question is why not choose c# for this? What’s the apprehension here if any?