You know, that is my immediate reaction as well. But if I'm more introspective it did teach (or reinforce) a few lessons that are worth knowing. Dependencies

You know, that is my immediate reaction as well. But if I'm more introspective it did teach (or reinforce) a few lessons that are worth knowing. Dependencies have a cost (even if they are easy to manage). Abstractions have a cost (even if they are easy to write). Consistency is often better than best case performance. Code style doesn't matter. Scriptable tools are invaluable. Make ain't that bad. Enjoying your team is more important than enjoying your language. All told, I don't think Go will ever be my first choice, everything else being equal, for anything beyond what I like to call "bash++". But it also won't be a reason I don't take a job, or move to a team and if my team wants to use it, I won't object too strongly.