Not the mono runtime; the fact that there are two runtimes.
The official MS one, and the Mono one, and although they're kind of compatible, in that your C# can be compiled to run on either of them (mostly, sometimes, if you haven't done anything fancy, if you're not using MVC, if you're not using a UI layer that isn't portable, if the version of mono you're using from A is the same as from B ( >_> unity...) ), this is FAR away from the java JVM, where you can ship an application that just runs on all the platforms.
Don't get me wrong, you can do that with C# too... if you use Mono only, and flip off the official M$oft .Net runtime.
...but the mono runtime is behind the curve, always playing catchup to the 'official' runtime, supporting a subset of the features, and everywhere runs different versions of the mono runtime. It's a mess.
You've got to admit, the JVM is 100% superior in this regard.
I suppose you've never had a problem with two JVMs that ran a package but didn't behave quite the same way, to disastrous effect? Or dealt with software that only worked with one very specific version of the JRE that was exclusive from the equally specific JRE required by another bit of software?
To compare Mono to the MSFT CLR and call it rubbish by way of contrast to Java-land strikes me as hilarious. I'll choose .NET every time given that choice...
>I suppose you've never had a problem with two JVMs that ran a package but didn't behave quite the same way, to disastrous effect?
Only at the very limited level of "versions of the JVM before x have a bug that makes this package not work.
>Or dealt with software that only worked with one very specific version of the JRE that was exclusive from the equally specific JRE required by another bit of software?
No, never. I know one should never overestimate enterprise software vendors, but you'd have to try really hard to make something that crap.
I use HotSpot and JRockit. There's performance differences between the two but I've yet to run into something that works on one and breaks on the other.
Well there's weirdness between Oracle and OpenJDK, thought to be fair I haven't had a problem with OpenJDF for a while. I don't imagine it's that unusual to find a server running Oracle JVM though.
In all seriousness most Java devs. regard the OpenJDK package as "that weird jvm that comes with the OS that nobody actually uses". First thing we do is download the latest JDK from Sunoracle.
What? That's not true. "Most Java devs" (that I know) prefer Linux and primarily utilize OpenJDK for development. (Deployment is a mess left to other people).
Really? No one uses Linux? And you're talking about Java and JVMs? That just looks silly.
I only develop on Linux, think you got confused by the way I phrased it. I meant that hardly anyone uses the OpenJDK package, not that hardly anyone uses Linux.
I'm (among other things) a Linux Java dev, and for what is worth from my anecdotal point of view, neither me nor anyone I know users OpenJDK. Both development and deployments happens with Oracle stuff.
Not the mono runtime; the fact that there are two runtimes.
The official MS one, and the Mono one, and although they're kind of compatible, in that your C# can be compiled to run on either of them (mostly, sometimes, if you haven't done anything fancy, if you're not using MVC, if you're not using a UI layer that isn't portable, if the version of mono you're using from A is the same as from B ( >_> unity...) ), this is FAR away from the java JVM, where you can ship an application that just runs on all the platforms.
Don't get me wrong, you can do that with C# too... if you use Mono only, and flip off the official M$oft .Net runtime.
...but the mono runtime is behind the curve, always playing catchup to the 'official' runtime, supporting a subset of the features, and everywhere runs different versions of the mono runtime. It's a mess.
You've got to admit, the JVM is 100% superior in this regard.