News for hackers. Stuff that matters.

A comment on The State of Go: Where we are in February 2016. Parent comment

Re:The State of Go: Where we are in February 2016 by geodel on Wednesday February 03, 2016 @12:12PM (#11027703)
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/me...

[ Parent | on HN ]
Re:The State of Go: Where we are in February 2016 by pjmlp on Wednesday February 03, 2016 @01:25PM (#11028414)
Back 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.

[ Parent | on HN ]