As someone who avoids IDES, I've always been wary of languages which require an IDE to allow people to work on a project or even make even smallest amount of ch

As someone who avoids IDES, I've always been wary of languages which require an IDE to allow people to work on a project or even make even smallest amount of changes on a project and rebuilding. The verbosity and oh-so-explicit-my-brain-hurts overt structured with too many layers of abstractions actually prevents me from fully understanding what is happening. Code reviewing for me becomes a chore where I can't focus on the purpose of the code. I can't read it - understand it and know that my fellow engineers have understood the task. Underneath the LoC, the Maven/Gradle mess, the structure and the plugins -- where do I see the engineer's intent? Not only is Java extremely verbose and requires an IDE to write the code for you - it is also very complex, hence hard to understand. Developers spend most of their time reading code, if 70% of it is autogenerated (imports and layout and code completion to find the right 50 letter function) so why do we make them read machine generated code just to understand what, in this example, should have been 58 lines of code but instead becomes a ~440 lines long, 7 file/entity monster when a few simple functions would have sufficed. What justifies the complexity of Java? I think this decade belongs to Clojure for the JVM.