cheeserquick poll: if you were to update to a new version of a library you'd been using and the new version has a trasitive on kotlin that it hadn't had before, would that bother anyone and if so, how much?
ParaDepends on the general size of the project in general; does it explode the dependency tree, does it slow down compilation significantly, all that. Then of course if the library becomes unidiomatic due to interop requirements, I'd probably look for alternatives.
kcomhnalleh... can't we exclude transitive deps though?
kcomhnallbetter question - is this kotlin dep required?
ParaOther people's mistakes are not my problems to fix - if a library includes unneeded deps, then that library is broken.
kcomhnallwill likely be broken for sure if its required and removed
kcomhnallcheeser: just curious what's the library in question?
DoofusCanadensiserr, a pure Java app now has kotlin deps in it
BombeJust another day in dependency land.
NeXeNcheeser: beyond the obvious bloating, it wouldn't matter much if you already use kotlin-stdlib for stuff. but if it's just like they wanted to have one little thing in kotlin, then it is probably not going to be adding any benefit
cheeseragreed. i have a whole subsystem that used to be a separate thing but i'm merging in to the main project and I was on the fence about converting it back to java but I'm in the process of doing that now.
cheeseror at least, instructing claude about it. :)