Hacker News Reader

Go's VM consume less resources, so we gets more RAM. Fore back-end processing, it's a supercool trade off.

First of all; Go is compiled to binary form, it doesn't run on a VM (yet?).

Second of all; the words you're looking for are "get" and "For", not "gets" and "Fore". Sorry to be a grammar nazi, but I'm just calling it as I see it, and this isn't Reddit or 4chan (yet?).

For others wanting to know more about Go's garbage collection, it used a conservative GC up until recently, but heaps of work has been done to make the GC precise, so we don't get leaks on 32-bit platforms. As far as I know this GC change has yet to be released (current release is 1.0.2, and the changes should be in the next release).

That said, if you clone tip and build from there (it's remarkably stable) you should be able to see the differences.

For some people, VM means everything that the language offers to the programmer at runtime. Sometimes libraries, usually GC. Even malloc could be considered VM.

Those people are wrong. Malloc and crt0 aren't VM's.

It's about what "some people think". This is Computer Science. Things have a name and a definition.

By your logic "for some people, Earth is flat".

Some people are wrong, the word they are looking for is runtime, not VM.

that's what i was looking for.

Reply on news.ycombinator.com