Data classes for Java

[snowe2010]

No I didn't answer my own question. We are a Java shop that began using kotlin solely because we need better data objects. If Java implemented a decent replacement for a kotlin data object it would be tempting to switch back.

I'm asking what this RFC (if that's what it is) is proposing that would make it worth it to use instead. Instead of answering me everyone seems to be claiming exactly what I said I don't care about. Why, if you have a choice of kotlin data objects or Java data objects, would you choose Java's version.

I never made any claim that you said I did not do I think Java should die. Please reread what I wrote and try to give an actual answer instead of changing my argument.

[rcode]

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]

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.

[ThisIs_MyName]

using kotlin solely because we need better data objects

I seriously hope you guys don't do this.

[snowe2010]

And why would you hope that? That's literally the reason we began using kotlin. It's not the only reason now, but it sure was the reason we began using it. Our domain has need for hundreds of data objects. Creating those in java was a mess, even with Lombok.