I understand the concern for mobile/embedded stuff and don't know much about how well Java does there.
However, when a half gig of RAM for a server costs well under $100, it just doesn't matter much for regular 'ol server apps. Even a "bloated" J2EE app doesn't usually require more than a gig of heap (unless you're doing massive, in-memory caching). Yeah, it's nice to use less memory, but there are 50 other things I'd give equal weight to (the availability of libraries being about 25 of those 50).
As I write this comment, I am tuning a Java rules (rete) app that is using an 11 gig heap :)
Comments
And the memory footprint thing....
I understand the concern for mobile/embedded stuff and don't know much about how well Java does there.
However, when a half gig of RAM for a server costs well under $100, it just doesn't matter much for regular 'ol server apps. Even a "bloated" J2EE app doesn't usually require more than a gig of heap (unless you're doing massive, in-memory caching). Yeah, it's nice to use less memory, but there are 50 other things I'd give equal weight to (the availability of libraries being about 25 of those 50).
As I write this comment, I am tuning a Java rules (rete) app that is using an 11 gig heap :)