Tonkyhonk wrote:what about these forums
Haha, well, I didn't write them myself, after all, and there is a reason why I don't modify them much. :)
Tonkyhonk wrote:what about these forums
loftar wrote:N'est ce pas?
- Has the better JIT,
loftar wrote:
- Has a Linux implementation that doesn't suck, and
- Has an ecosystem that isn't Windows-centric.
romovs wrote:Huh? Both C# and Java have near identical performance (some things perform marginally better in C# others in Java). The superiority of one JIT over the other is not so
romovs wrote:The situation is finally bound to change in the very near future.
loftar wrote:Admittedly, the first one is Mono rather than MS .Net, but it is my understanding that they are comparable in performance these days.
loftar wrote:That's fairly irrelevant, however, since the client is already written. I'm not going to rewrite it to another language which is basically the same thing anyway.
romovs wrote:the difference would be very minimal, similarly to the second .NET vs Java benchmark in your post.
romovs wrote:Uh I guess you need to really dig into their JIT implementations in order to come with some sort of educated answer regarding JIT performance
romovs wrote:Some of the Java lang features make me cry sometimes.
windmaker wrote:this guys dont know the beauty of Ruby.
loftar wrote:romovs wrote:the difference would be very minimal, similarly to the second .NET vs Java benchmark in your post.
You mean that benchmark where Hotspot was consistently beating .Net by anywhere from 1.4× to 2.5× in all but one benchmark?
loftar wrote:Was my statement on deoptimization not enough "digging" for you?
romovs wrote:Are we referring to same benchmarks? In this one C# .NET beats Java in 6 out of 9 cases as far as I can see. Although it is 3am already and my retard mode might have kicked in so it's possible I am overlooking something...
loftar wrote:In the second one, Java on Linux is beating .Net by a fair margin, while .Net is beating Java on Windows by a fair margin. I'm guessing this is because their Java on Windows benchmark uses the client JIT, which noone should ever use (but 32-bit Java on Windows defaults to it).
romovs wrote:It's wasn't. I presume JIT performance isn't determined merely by one feature or lack of thereof.
romovs wrote:On the surface both seem to perform on equal levels.
loftar wrote:In particular, I consider myself first and foremost to be using the Java VM before I'm using the Java language, and if I were to be using C#, I would likewise consider myself to be using the CLR rather than C# itself, and the JVM just seems to be so much better documented and defined than the CLR. I've still to find even a reasonable overview of the latter -- precisely like all other Microsoft tech that "isn't meant to be used directly", it seems to be quite obscure and hard to get at.
Generally, my opinion of Java is that the VM is pretty nice (though it's not as if I couldn't find things to complain about if you wanted me to), but that the language sucks.
@YarPirate: there are plenty tools out there to reverse engineer software ran through an obfuscator.
Users browsing this forum: No registered users and 1 guest