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 On Aug 12, 2:48 pm, phil swenson <[email protected]> wrote: > http://eblog.chrononsystems.com/xmx-is-hurting-the-usability-of-java > > I've been saying this since I first discovered the terrible > OutOfMemoryException in 1999. Xmx makes java inherently unstable. > You can't rely on your app to stay up until you find the magic Xmx > setting. WTF!? > > Dick/Carl/Tor/Joe - when you talk to Mark Reinnhold, can you bring this up? -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. 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.
