I haven't used Java for a long time myself - and am not up to date with it's current featureset. I know I used to like coding in Java back in 2000/2001, but my

I haven't used Java for a long time myself - and am not up to date with it's current featureset. I know I used to like coding in Java back in 2000/2001, but my professional career demanded switching to C/C++ - which I did and also said goodbye to a few years ago. Anyway - something I posted yesterday in the "Java for everything" thread here: > My view of Java may be a bit biased, since I also tend to look at things from the sysadmin pov nowadays. I can only tell that I never disliked Java until I had to take care of the monstrosities the Java developers bring to life, and mind you - I started out as a Java dev back in 2000. > > The main issue I have with Java is the JVM and memory usage and leaks. No matter what people claim - no memory leaks in Java is a fairy-tale. We run both custom C++ and Java services (about 50/50) on a few hundred servers - and I cannot find a single issue in our ticketing system related to memory problems with any of our C++ services. Java services? Every. Single. Week. When I get an alert some JBoss unexpectedly died or became unresponsive - "java.lang.OutOfMemoryError" is most likely going to be the problem. A lot of those are permgen space errors, and yes you can try all the "fixes" like increasing the permgenspace, permgensweeping, enabling class unloading, ... but these don't always fix the problem and slow down your services. Every time this happened in our own services, this had to be fixed by our developers. It takes weeks to locate the problem, and you end up deploying new versions, upgrading JBoss, JSF, Bouncycastle, ... whatever. After a while dealing with crap like this - you start avoiding projects using the JVM (although elasticsearch is pretty nice)