Link Details

Link 964933 thumbnail
User 252549 avatar

By ivom2gi
Published: May 08 2013 / 21:32

If you have thought that for Java it will all be about Write Once, Run Anywhere then – make a second guess. It all falls apart the very same minute you create something truly low-level and optimized to the last possible bit. Suddenly all kind of unexpected small details start to matter, such as the garbage collector selection, minor differences in the classloader implementations or the way JVM vendors have decided to interpret certain parts of the JVM specification.
  • 7
  • 6
  • 998
  • 1062


Add your comment
User 161039 avatar

mheath replied ago:

0 votes Vote down Vote up Reply

No duh. Java strives for write once, run everywhere not optimize once be optimized everywhere.

User 252549 avatar

ivom2gi replied ago:

0 votes Vote down Vote up Reply

In the sense you are completely correct, most of the applications do not go to the extremes Plumbr is forced to deal with. But the usual Java EE applications also tend not to be happy with the switch from for example 32-bit Windows to the 64-bit Mac OS X. Usually you still find one or two things you need to tweak.

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (7)

Voters Against This Link (6)

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java