3 ms·

I don't want to sound like i am downplaying you understanding of the JVM. But i still have to ask : efficient as compare to what ? From having played around t

I don't want to sound like i am downplaying you understanding of the JVM. But i still have to ask : efficient as compare to what ? From having played around the JVM, and spent quite a bite of time optimizer large spark workload , from the limited Monomorphization, to memory and cache inefficient object model, to the limited inlining depth, absence of code compaction ( for i-cache performance), the poor registor allocator etc... the JVM is really not up there. I think it only shines when compare to things like go/python/javascript that the JVM can appear to be great.

pjmlp 3y ago
Compared to doing distributed systems in DCOM/CORBA using C and C++ for example, that is one of the reasons it took off. Many that like to bash Java EE, have no clue how bad it was before it came to be, it wasn't only Sun's marketing pushing it. It isn't by accident that RMI had interoperability with CORBA.
- soulbadguy 3y ago
  I am not sure how this is an answer the my argument. However saying that distributed system in JAVA EE are more performant that in C++ ( i am no familliar with DCOM/CORBA but i do know other libraries and system ) is news to me. And again, the success of JAVA in the 90 and 00 can also be explained by better tooling, safer language,better x-platform stories,better libraries etc... etc... Saying that java/jvm are not particularly performant is not bashing ... java/jvm have other great things going on... performance just isnt one of them
  - pjmlp 3y ago
    I guess if what one is measuring FPS for AAA, then surely not. Naturally not having a clue about how to write proper Java code (for loops instead of System.arraycopy()), use profilers, use JIT caches with PGO feedback, not understanding how to allocate off heap, not using JNI to avoid writing everything in C or C++ with their own set of issues, doing background stuff on main threads,...also helps some Java applications not being performant.

pjmlp 3y ago

Compared to doing distributed systems in DCOM/CORBA using C and C++ for example, that is one of the reasons it took off. Many that like to bash Java EE, have no clue how bad it was before it came to be, it wasn't only Sun's marketing pushing it. It isn't by accident that RMI had interoperability with CORBA.

soulbadguy 3y ago
I am not sure how this is an answer the my argument. However saying that distributed system in JAVA EE are more performant that in C++ ( i am no familliar with DCOM/CORBA but i do know other libraries and system ) is news to me. And again, the success of JAVA in the 90 and 00 can also be explained by better tooling, safer language,better x-platform stories,better libraries etc... etc... Saying that java/jvm are not particularly performant is not bashing ... java/jvm have other great things going on... performance just isnt one of them
- pjmlp 3y ago
  I guess if what one is measuring FPS for AAA, then surely not. Naturally not having a clue about how to write proper Java code (for loops instead of System.arraycopy()), use profilers, use JIT caches with PGO feedback, not understanding how to allocate off heap, not using JNI to avoid writing everything in C or C++ with their own set of issues, doing background stuff on main threads,...also helps some Java applications not being performant.