3 ms·
That's funny, when I talked to Neha (ex-Linkedin, cofounder of Confluent) she explicitly denied this meme about moving away from Scala. The new Kafka client li
by kod 10y ago
That's funny, when I talked to Neha (ex-Linkedin, cofounder of Confluent) she explicitly denied this meme about moving away from Scala.
The new Kafka client library is in Java just to reduce the number of dependencies, the server is still written in Scala. Strangely, using Java hasn't stopped Confluent from making breaking changes on dot release of the client... which really puts the lie to your explanation.
- pfarnsworth 10y agoI specifically said the Scala clients are being deprecated. Go ask Neha to confirm this.
- kod 10y agoNo, you specifically said they're being deprecated because of maintainability issues inherent to scala, which is not true.
- pfarnsworth 10y agoNope. They were getting sick of having to maintain different versions of the Scala clients because of breaking changes, as per a Kafka committer.
- kod 10y agoEven if some random kafka committer that you can't source believes that, the reasoning doesn't add up: SBT makes it fairly straightforward to cross publish for different dot releases of Scala, and libraries in the Scala ecosystem do it all the time. Scala dot releases are far apart. It's been over 2 years since 2.11, and 2.10 released in 2012. By contrast, the JAVA client that the Kafka project published in November is already undergoing breaking changes for the current release candidate. It's pretty clear that avoiding breaking changes is not an overriding concern for them, and even if it is, it's equally clear that Scala was not the inherent problem.