4 ms·
Java itself is fine. It's very popular--and that's the biggest problem. Not the language as such but the developer ecosystem around it. I am dead tired of seein
by sidlls 7y ago
Java itself is fine. It's very popular--and that's the biggest problem. Not the language as such but the developer ecosystem around it. I am dead tired of seeing 80-character camel-case function and variable names, annotations that hide critical functionality of the code, stack traces dozens or hundreds of lines long because of the amount of indirection and poorly conceived configuration "languages" used to support dependency injection so developers can save a few characters of typing or mask dependencies and complexity, etc.
The language may be fine, but it has been appropriated into the worst sort of terrible programming paradigms one might imagine.
- datavirtue 7y ago"80-character camel-case function and variable names" Isn't that a good thing? Tell all of us developers who write clear, clean code why you think that is bad? I don't ever get to 80 characters but I do write methods names that describe exactly what they do. If I can write it comfortably then I know I tried to do too much in the body.
- Cacti 7y agoWe aren’t talking about Java the language. We are talking about the JVM.
- ptx 7y agoThe terrible programming paradigms are workarounds for the terrible language. I read an old blog post about Spring's @Required annotation versus plain constructor injection and typed out a small example to get a feel for it – a simple class with one required and one optional dependency – which resulted in 23 lines of plain Java with constructor injection, or 16 lines of Java with Spring @Autowired magic, or 7 lines of Kotlin – no magic needed.