> I haven't met anyone migrating from say, Play to Spring thanks to Kotlin's support. Hi, now you have :) Well, Vert.x and Ktor, not so much Spring Boot. It's

> I haven't met anyone migrating from say, Play to Spring thanks to Kotlin's support. Hi, now you have :) Well, Vert.x and Ktor, not so much Spring Boot. It's mainly because effective and readable Scala requires a lot more discipline and experience than effective Kotlin for a Java developer. If we'd started solely with experienced Scala devs then I suspect we wouldn't have had an issue. There is, also, the problem of footguns - we've inherited a large Scala codebase from a sister company, and they, unfortunately, let the devs run free. So there's large amounts of hard to debug, hard to read, Scala magic going on. Implicit classes, inherited three levels deep! Macros! Why? Because they could!