>By having an overly simplistic language, you end up pushing more complexity onto the programmer and into the code base. There is no free lunch. Sure, I just d

>By having an overly simplistic language, you end up pushing more complexity onto the programmer and into the code base. There is no free lunch. Sure, I just don't see this as a problem. As a result you have a) a number of third party packages to chose from depending on your needs\opinions b) you have a more verbose codebase, some people find it harder to deal witih while I find it easier to deal with. >compared to having to read many lines or pages to understand what's going on. Different people different ways of thinking I guess. In my eyes Java code looks to much like a specification in for of a code. Easier to do a code review but harder to actually understand how it works. And I personally need this dive into internals to actually feel confident about the code. >Could you elaborate on exactly what complexity in Java you're referring to? I don't have too much experience in Java, but from what I've seen - Java has too many abstractions and OOP for the sake of paradigm and nothing else. UPD: adezxc's comment is a good addition to mine