3 ms·
> the JVM's awful GC This just makes it seem like you are trolling. JVM devs have done more to advance state of art in this area than any other language. The p
by james-mcelwain 7y ago
> the JVM's awful GC
This just makes it seem like you are trolling. JVM devs have done more to advance state of art in this area than any other language. The problem is that most JVM apps just produce too much garbage, not necessarily that the algo itself is awful.
Either way, there's no such thing as an optimal GC algorithm, just different trade-offs depending on your use case. Not everyone cares about latency.
- geodel 7y ago> The problem is that most JVM apps just produce too much garbage, This is strange way of saying that Java the language and most frameworks around it force apps to generate this much garbage.
- james-mcelwain 7y agoNo, it's a way of saying that Java != the JVM. The JVM's GC is not "awful" precisely because so many Java frameworks are awful.
- nvarsj 7y agoI stand by that - I really think the JVM has a bad GC, and it has cost businesses billions probably. There is no trade off here - the JVM & Java have incredibly high memory requirements due to poor design - and this leads to all kinds of issues (like the bad GC latencies). No other language has this kind of problem as badly as the JVM does, even other GC languages. And we shouldn't accept this anymore - look at how much better golang's GC is for real world usage.