this post was submitted on 22 Nov 2023
37 points (86.3% liked)

Programming

16971 readers
736 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

In this article, we’ll debunk the notion that Java is a relic of the past and showcase the language’s modern features, thriving ecosystem, and unwavering presence in enterprise and open-source communities.

you are viewing a single comment's thread
view the rest of the comments
[–] pprkut@programming.dev 5 points 9 months ago* (last edited 9 months ago) (1 children)

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 alternative suggestions that are nicer to use in Java?

[–] huginn@feddit.it 2 points 9 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.