3 ms·
Erlang still uses GC, however because there is no shared memory (except ETS[1]), the GC can run independently for each process. This is eons better than JVM[2],
by deno 14y ago
Erlang still uses GC, however because there is no shared memory (except ETS[1]), the GC can run independently for each process. This is eons better than JVM[2], with all the benefits of not having to worry about manual memory management. It’s not C, though, and I don’t believe author implies that in any way. In fact he acknowledges the exact opposite.
[1] http://www.erlang.org/doc/man/ets.html http://www.erlang.org/doc/man/ets.html
[2] http://www.javacodegeeks.com/2011/04/erlang-vs-java-memory-architecture.html http://www.javacodegeeks.com/2011/04/erlang-vs-java-memory-a...
- pron 14y agoI wouldn't say it is "eons better than the JVM". The JVM GC, especially the new G1 collector, is probably the most advanced and performant garbage collector available on any platform. Erlang, however, does provide isolation. There are versions of the JVM for hard real-time applications (Erlang is for soft real-time only), that provide explicit memory management, and a very fine-tuned GC, like this one: http://java.sun.com/javase/technologies/realtime/index.jsp http://java.sun.com/javase/technologies/realtime/index.jsp I know of some defense applications that use it.
- deno 14y agoI knew that JVM had some advanced GCs available, including few commercial ones, but I didn’t know about Java RTS. That’s great.