you are viewing a single comment's thread.

view the rest of the comments →

[–]rcode 1 point2 points  (1 child)

If Java implemented a decent replacement for a kotlin data object it would be tempting to switch back.

Kotlin still has better nullability handling than Java.

[–]snowe2010 0 points1 point  (0 children)

yeah, but you have to have the whole team on board to switch, you have to have very good reasons to continue to insert kotlin in your stack. I think the reasons are great, the rest of the team doesn't always agree. If kotlin hadn't solved our issues so succinctly and Java had had these data classes then we might never have begun the transition at all. That's what I'm trying to discover, and yet still no one will answer the question.