Linked by kragil on Wed 23rd Jan 2013 20:26 UTC
Thread beginning with comment 550163
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by Laurence
by Hiev on Wed 23rd Jan 2013 21:52
in reply to "RE[3]: Comment by Laurence"
RE[5]: Comment by Laurence
by saso on Wed 23rd Jan 2013 23:24
in reply to "RE[4]: Comment by Laurence"
And that it will make memory management of your code largely unpredictable. And introduce random latency bubbles as the incremental mark&sweep collector decides to run. And that you might start hitting into various OS-enforced resource allocation limits (number of open file descriptors, for example).
GC is good for some things (like large non-performance-critical CRM systems, ERP systems, web apps, etc.), but shit for cases where you need to make careful decisions about available resources and runtime (OS kernels, databases, HPC, etc.).
RE[4]: Comment by Laurence
by Laurence on Wed 23rd Jan 2013 22:24
in reply to "RE[3]: Comment by Laurence"





Member since:
2008-12-26
Go is not managed language, even if it's garbage collected. It compiles directly to native code that is executed on the CPU (i.e. no interim "bytecode" representation is used).