Hi Seb. In my team we are migrating things to Kotlin because we find it much easier to deal with. It's like the best of both worlds, but you do give up on Flink Scala serializers, since the only way to get Kotlin Data Classes working is by making them a POJO (or implementing your own TypeInfo). You do at least gain Evolution support.
We've found that Kotlin + Gradle are a great combination, and we end up with quick compile times, a much simpler build config (compared to Maven and SBT). Another thing is that we've found that the macro createTypeInformation can be dangerous, because sometimes it may fallback to Kryo on classes you don't expect it to. Those implicit behaviors we see in Scala have caused us some headaches and we prefer to explicitly type things in the Data Stream. Just personal preference, but pointing it out in case it's useful to someone. Hope this helps! On Mon, Jan 24, 2022 at 7:15 AM seb <sebunderthe...@protonmail.com> wrote: > Hi there, > > I am getting started with Apache Flink. I am curious whether there is a > clear winner between developing in either Scala or Java. > > It sounds like Flink is typically slower to support new versions of Scala > and that Java development might have fewer quirks. > > What do you think? I have experience coding in Scala, but I am more than > happy to learn Java. > > Thanks in advance for sharing your thoughts! > > Best, > Sebastian >
