3 ms·
Write Kotlin instead so you can have a method named `this method will calculate the sum of two integers`! I don't think Java has a naming problem per se, I thi
by jeroenhd 4y ago
Write Kotlin instead so you can have a method named `this method will calculate the sum of two integers`!
I don't think Java has a naming problem per se, I think the focus on inheritance and other OOM principles just make it very easy to overengineer your solutions.
Things like getters and setters (and the fact Lombok still isn't just part of the language itself) annoy me much more. At least records fix some pain points.
- tapotatonumber9 4y agoExactly ! In my experience OOM certainly seems to be a Java key principle. (Currently replacing a Java application with one written in Go).
- NERD_ALERT 4y agoI’ve personally enjoyed using Immutables even more than Lombok. It produces generated java classes instead of a JAR when you build so it’s easy to view. https://immutables.github.io/ https://immutables.github.io/