I've ported a lot of services from kotlin to rust. In my experience the kotlin code is about half the size of rust, and has about 200 mb + 2*x the memory overhead. Kotlin code probably takes about half of the time (or less) to write compared to rust as well, but you're not quite as sure that is it bug free as the rust code once it's done.
An important distinction is also whether you were using Kotlin-JVM or Kotlin-native. I'd imagine the native version doesn't have the same memory impacts. (But you also don't get the JVM advantages).
My Thoughts on Kotlin: Perspectives after 4 years
11–12 of 12 posts
Re: My Thoughts on Kotlin: Perspectives after 4 years
#12I've ported a lot of services from kotlin to rust. In my experience the kotlin code is about half the size of rust, and has about 200 mb + 2*x the memory overhead. Kotlin code probably takes about half of the time (or less) to write compared to rust as well, but you're not quite as sure that is it bug free as the rust code once it's done.
That's a great point and I'm not sure why the memory usage/performance didn't come to mind when writing this. It's probably because, like most JVM related things, it fits into the "good enough" bracket. Most things running in the JVM are definitely not on the forefront of either CPU or memory performance. I haven't done personal estimates, but your 200 mb + 2*x estimate feels in line to what I'd expect when compared…