Lombok will shrink the 200 lines of getters and setters to one or two. It has its own pitfalls of course, but IMO it’s definitely worth it.
Comment on Is Java Still Keeping Up with Modern Programming Languages
huginn@feddit.it 7 months agoI’m normally working in Kotlin when coding because I do Android development. I’ve had the misfortune of taking up some slack in a greenfield backend project and holy God is it miserable.
Everything is harder to read, every basic data model is 200 lines of getters and setters, multithreading is painful, basic transformers require separate class declarations. And that doesn’t even touch on the horrific experience of using Jackson to handle json serialization.
BlueBockser@programming.dev 7 months ago
huginn@feddit.it 7 months ago
Corporate standards.
I’m pushing for no half measures: it’s Kotlin or bust.
BlueBockser@programming.dev 7 months ago
Definitely agree that Kotlin is so much better than Java + Lombok, but it’ll take a lot of time for all the existing Java projects or migrate to Kotlin or reach EOL. In the meantime, it’s hard to avoid the occasional Java project…
huginn@feddit.it 7 months ago
Sure but you can also just drop kotlin into any Java codebase. It’s a single line maven import and the entire company already uses Intellij
pprkut@programming.dev 7 months ago
I felt the same way coming back to Java from Kotlin. The more streamlined syntax of Kotlin is so much more comfortable to read and write. That being said, I never had an issue with using Jackson for JSON serialization in Java. I’m curious what issues you have encountered and if you have any suggestions that are nicer to use in Java?
huginn@feddit.it 7 months ago
I’m not sure there’s much that is better or worse than Jackson. When I worked exclusively in Java I was always using GSON and did not remember having so many hoops to jump through. Could just be my bad memory though.
I just feel like when I’m doing Java work I spend 90% of my time on useless boilerplate.