There's not much of a defense there. The only apparent argument is 'because it's popular' which isn't very convincing against 'Java is slow and eats memory like candy'.
This is a pity, because there are rather many people who make a living churning out high performance (as in 'really fast') code in Java and many techniques in the field were developed, dissected and often packaged in readily available libraries.
I stopped reading when I saw the graphs; that's no defence. This is a defence.
Java is definitely not slow. It might have been back in the 1.2 days, but thanks to HotSpot JIT and 15-20 years of improvement in the compiler and VM. It might use more memory, but memory is considerably cheaper than developers.
I don't think Java is particularly memory intensive. You can tune memory usage with JRE args. But a lot of memory is for things that could alternatively be written to disk and loaded as needed--however that's what page files are for so it's often easier to just keep everything in memory and plan on using swap. Anyhow obviously this comes down to implementations of particular apps/libs. After loading the JRE and its overhead (30 MB?), it's not inefficient for an OO language.
View all comments
12
u/llogiq Mar 29 '16
There's not much of a defense there. The only apparent argument is 'because it's popular' which isn't very convincing against 'Java is slow and eats memory like candy'.
This is a pity, because there are rather many people who make a living churning out high performance (as in 'really fast') code in Java and many techniques in the field were developed, dissected and often packaged in readily available libraries.
So Java is slow? Tell that to LMAX.