I agree that Java isn't fun or productive, but I'll qualify that statement with "for me". I really do believe that the reason we have programmer holy wars is b

I agree that Java isn't fun or productive, but I'll qualify that statement with "for me". I really do believe that the reason we have programmer holy wars is because we approach problem solving in different ways. The way I approach solving a problem with a computer program is almost incompatible with the Java programming language. And, no- this is not a thinly veiled way to shit on object oriented programming. I can work in an object oriented paradigm just fine. It's just Java specifically that doesn't work for me. Here are some examples that constantly bother me when writing Java: * Null. Enough said. * Writing value types used to be very tedious and bug-prone before Records. I haven't written Java with Records yet, but I'm glad to know that they'll be there if/when I do Java again. Even for an object-oriented architecture, value types can be useful and I use plenty of them. * Type erased generics are painful. Especially with interfaces. * The number and arithmetic APIs are incredibly frustrating. No unsigned numbers, silent wrap-around on overflow, silent data truncation on casts, etc. I have zero confidence that my Java code that deals with numbers is robust at all. I'm sure that many programmers don't even notice these things, because they way they interact with program design is just different than my way. But when I write Java (or mostly any JVM language) one or more of these issues are on the forefront of my mind with almost every single line of code I type. It's almost unbearably frustrating.