3 ms·
It is straightforward because Go has first class value types which are most likely to be on stack vs Java where everything except primitives are reference type
by geodel 11y ago
It is straightforward because Go has first class value types which are most likely to be on stack vs Java where everything except primitives are reference type which are most likely to be on heap. Also Java data structures are really bloated.
https://www.cs.virginia.edu/kim/publicity/pldi09tutorials/memory-efficient-java-tutorial.pdf https://www.cs.virginia.edu/kim/publicity/pldi09tutorials/me...
- pjmlp 11y agoBack when Java was introduced I was disappointed that they decided to ignore value types, specifically given that Cedar, Modula-3, Eiffel and Oberon variants all had them. Also that they went VM instead of AOT like those languages main implementations. Oh well, at least they are now on the roadmap for Java 10, 30 years later.