News for hackers. Stuff that matters.

A comment on Erlang/OTP: Garbage Collector. Parent comment

Re:Erlang/OTP: Garbage Collector by omginternets on Saturday April 01, 2023 @02:24PM (#35402656)
It’s a GC tuned for imperative languages that prefer mutation over allocation, which is the exact inverse of what BEAM needs.
[ Parent | on HN ]
Re:Erlang/OTP: Garbage Collector by pron on Saturday April 01, 2023 @03:28PM (#35403285)
OpenJDK's GCs do have elaborate mechanisms to support mutation, but if they're unused they impose no extra overhead.
[ Parent | on HN ]
Re:Erlang/OTP: Garbage Collector by omginternets on Saturday April 01, 2023 @10:44PM (#35406622)
I think you may be missing the point. What the JVM doesn't have is elaborate optimizations to support copies, e.g. a generational GC.
[ Parent | on HN ]
Re:Erlang/OTP: Garbage Collector by NobleExpress on Sunday April 02, 2023 @12:13AM (#35407095)
Hm? G1 is a generational GC? And so is Serial/Parallel. And work on generational ZGC is ongoing [1]. Not sure what you're referring to here.

[1]: https://openjdk.org/jeps/439

[ Parent | on HN ]
Re:Erlang/OTP: Garbage Collector by omginternets on Sunday April 02, 2023 @05:31PM (#35415462)
I was mistaken!
[ Parent | on HN ]
Re:Erlang/OTP: Garbage Collector by pron on Sunday April 02, 2023 @07:20AM (#35409372)
The JVM has a selection of four generational GCs. Two of them are the most sophisticated GCs available anywhere.

It's not a matter of some unique brilliance. Java is simply in such high demand that it has the sufficient resources to have state of the art optimising compilers and GCs.

[ Parent | on HN ]
Re:Erlang/OTP: Garbage Collector by omginternets on Sunday April 02, 2023 @05:31PM (#35415459)
Really? I had no idea. Can you suggest further reading?
[ Parent | on HN ]