On Friday, August 12, 2011 11:37:15 PM UTC+2, mbien wrote: > > see it as performance optimisation. A GC impl which would have to deal > with fragmented, non continuous and resizing heap would have a hard > time to compete with the current VM. A JVM is a operating system for > java applications. You can't plug in new RAM brick in your system > easily at runtime for the same reasons. > > I would go even further and say that writing java applications with > unknown memory requirements is not that professional :P >
This is spot on. For large server apps. For client apps or quick command line tools, being forced to prepick total memory load (and treating the JVM that's going to start up to host your app as an OS-in-a-OS), is ridiculous. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/GqhNi5D-FqIJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
