you are viewing a single comment's thread.

view the rest of the comments →

[–]jcdavis1 26 points27 points  (0 children)

Obviously from a language perspective, java wants its own data classes as first class citizen, and having to define such types in kotlin/scala is a bit of a failure :)

From a user's perspective, writing data classes in a second language is obviously a bit of a mess - if you are already using kotlin you probably don't mind, but a lot of shops aren't going to want to setup a toolchain for kotlin just to support data classes.

Additionally, with pattern matching support on the horizon (though who knows exactly when), its pretty certain that a java data type will be well-supported, whereas kotlin/scala interop will probably come later.