2 ms·
> This is not an issue with the runtime Yes. But no. But yes. The code couldn't been written better to allocate less. But the runtime encourages cheap allocat
by viraptor 3y ago
> This is not an issue with the runtime
Yes. But no. But yes.
The code couldn't been written better to allocate less. But the runtime encourages cheap allocations you don't think about. But the runtime could provide/encourage tooling that makes it hard to make that mistake. But...
It all overlaps. Sure, JVM is cool and handles it, but also what JVM is influenced how people instinctively used it.
- winrid 3y agoMost people don't write Java games this way. If you look at any libgdx code examples people cache objects and use polling - you don't know how modern a VM the user will have especially on Android.