4 ms·
> Generally you don't care about memory management in Go at all I think this is true for the majority of devs, just as it is for any managed language (C#, Java
by GordonS 5y ago
> Generally you don't care about memory management in Go at all
I think this is true for the majority of devs, just as it is for any managed language (C#, Java...).
But sometimes you are working on something performance sensitive, and there minimising allocations can be a real problem.
- kgeist 5y agoAbstractions do have costs, no doubt. I just don't see the connection between "Go heavily uses interfaces which force heap allocation in the current implementation" and "1975 programming". How would one go from 1975 to current year? By stopping using abstractions? Isn't that exactly what 1975 programming was to begin with?
- GordonS 5y agoWell, yes, I have to agree that I don't see the link between allocations, abstractions and 1975 ¯\_(ツ)_/¯