3 ms·
Surely having a shared memory model increases the design space? Or is this about memory management performance? A benchmark should settle things in that case.
by BenoitP 4y ago
Surely having a shared memory model increases the design space? Or is this about memory management performance?
A benchmark should settle things in that case. Maybe it will be a draw! Erlang's almost-no-op deallocation vs Java's world-class JIT. Some applications are bound to be better suited to one specific side. I guess we'll see; but it cannot be denied that with Loom Java started to compete on a non-void part of Erlang's land.
- cogman10 4y agoIt's certainly a trade off. One thing erlang can do which java cannot is survive one of it's actors OOMEing. That kills the actor and not the VM. That comes at some extreme costs and implications to what the VM is capable of achieving, but it is something that's pretty impressive.
- lliamander 4y agoAbsolutely. And I'm not particularly partisan in this: I like Erlang ( the language in general as well as the concurrency model) and if Java moves closer to that then all the better.