3 ms·
That's more that go has an incredibly crude GC (which is in the process of being replaced, as far as I know), and less that it is fundamentally broken. Other l
by ori_b 15y ago
That's more that go has an incredibly crude GC (which is in the process of being replaced, as far as I know), and less that it is fundamentally broken.
Other language and GC implementations with a large shared heap can work fine. See, for example, Azul systems' JVM.
- nickik 15y agoAzul systems GC has Hardware and OS support that you don't have normally but I do generally agree.
- ori_b 15y agoThey have x86 ports of their system as well, I believe.
- nickik 15y agoThis is not really correct. As far as I understand the run a virtualization layer ontop of x86 that provieds these features. On would think that this is not worth it but there JIT and GC are so much better that it is worth it. This however is not as easy to use as typing "ruby dostuff.rb" or something. You need to run a full virtuall OS. I do really really hope that Intel does these Hardware changes it would help ever language with GC. (The OS would need to support that too but thats probebly a easyer then getting intel to add the feature)