

0·
5 days agoGood clarification, thank you. I guess it would still require some extra care when interfacing with plain Java libraries, but so does e.g. Kotlin. Cool implementation.
I’m a software engineering developer from Ottawa, Ontario, Canada.


Good clarification, thank you. I guess it would still require some extra care when interfacing with plain Java libraries, but so does e.g. Kotlin. Cool implementation.


There are many valid practical reasons to avoid Kotlin in certain circumstances (not the least of which being Russian ties). More tools for Java isn’t necessarily a bad thing. However I don’t really think it works. It reminds me of this blog post: https://www.javacodegeeks.com/2017/02/elvis-not-visit-java.html which I think accurately reflects many of my thoughts about null-safety in Java.
Just the historical Russian ties, which is enough for some people/organizations to avoid them. The biggest practical reason is the dependence on tooling. Kotlin is a great language, but loses a lot of its allure when you can’t use an IDE for whatever reason. It makes sense, given that its developed by a company whose main product is IDEs; but it can still be an issue in some circumstances.