quick poll: if you were to update to a new version of a #java library you'd been using and the new version had a transitive dependency on #kotlin that it hadn't had before, would that bother you and if so, how much?
@evanchooly that wouldn't really bother me at all.

@evanchooly yes and yes.

Full disclosure, I’m a member of the Apache Groovy team and I would also be bothered if a Java library suddenly added Groovy to provide internal behavior that Java could do. Same would apply to any other JVM language, they are not “just a library”.

@aalmiray that's kinda how I'm leaning, too

@evanchooly writing kotlin I would not notice, writing java I would be upset and look for alternatives.

A java core with optional kotlin sugar is appealing. Kmp has a different but interesting reach. The fact that conciling both requires a port most of the time is kind of irritating

@eskatos I've been there! I did the first kotlin apis for quarkus/panache back in my red hat days. It was annoying and I think I made some choices I regret.
@evanchooly oh, forcing a kotlin dependency on java consumers sounds like regrets to me :) If I would target both java and kotlin I would seek for a reusable core domain. In some cases, it might be possible to get kotlin common without stdlib code to ship to java consumers without dependencies. Some shading is probably needed for intrinsics.
@eskatos the kotlin panache was an opt in dependency so I didn't make *that* mistake 😁
@evanchooly good for you :) some projects out there did indeed make *that* mistake
@eskatos i was mulling it but Mastodon and bluesky talked me back from the ledge. Claude is converting that code for me as we speak.
@evanchooly would bother me very much