News for hackers. Stuff that matters.

A comment on Game Development in Go. Parent comment

Re:Game Development in Go by pjmlp on Monday January 26, 2015 @03:35PM (#8949404)
> You can always make the memory do exactly what you want it to, and there's always a clear path to get there from wherever you are.

Only if you write your own memory allocator, otherwise relying on the compiler provided allocator is no different.

[ Parent | on HN ]
Re:Game Development in Go by jblow on Monday January 26, 2015 @03:56PM (#8949509)
Which is why people who are serious about memory write their own allocators (or link preferred allocators with known behavior). It is an extremely common thing.
[ Parent | on HN ]
Re:Game Development in Go by pjmlp on Monday January 26, 2015 @04:47PM (#8949793)
Sure, I wasn't disagreeing with you per se, as I am well aware of your nick.

Just mentioning the issue for other readers, as many think malloc/NEW/Allocate or whatever is called, is fast.

[ Parent | on HN ]