Hacker News new | past | comments | ask | show | jobs | submit login

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 to "memory-tight" languages.




I agree and I'm not sure what language I would choose myself if it was up to me. In reality, we deployed to kubernetes with redundant instances and memory usage was the limiting factor with kotlin and it would not have been with rust.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: