[eropple]

I've been using Kotlin for a little while, as the backend language for the side project/maybe-startup I'm working on. I went with it because of my troubling tendency to write Scala code I can't read three weeks later, and in that I think Kotlin's a big success: the Java interop is good (still some weirdness around DI frameworks and non-nullable types, which is unavoidable if you're using something like Jersey with HK2), the language itself has most of the niceties I want, and I find that the tooling is really pretty good in general. And the Kotlin community, in my experience, has been really good (aside from...sigh...yet another Slack chat to be in), unlike the continuing and perpetual disaster of Scala whenever certain members of the This Should Be Haskell mafia are allowed near anyone who's just asking a question.

I miss things from Scala once in a while, but they're usually me being way too cute with my code anyway--good for tiny personal things, not for something I'm hoping I'm looking at three years from now, not just three weeks from now.

[wpietri]

That's helpful. I have this side Scala project, a long-lived daemon[1], that I've been meaning to rewrite in something else, as I've grown disenchanted with it. (Bruce Eckel and Paul Phillips contributed to that. [2]) But every alternative I could think of was not so appealing. I'll check this out.

[1] https://github.com/wpietri/sunrise

[2] https://news.ycombinator.com/item?id=10163446