Michael Christenson II
Nov 3 · 1 min read

One thing that gets set aside when you get used to Golang is this idea of thinking about memory usage as a pre optimization. We can all tell you from experience that you should first be looking at interfaces and memory usage from the start (and perhaps app layout to avoid import cycles), before things get away from you.

I appreciate the thoughtfulness of all your answers here and don’t think you are trying to steer anyone wrong. I just want you to have another set of things to consider as you build out your apps: memory matters so much in this language.