>Golang was designed for getting shit done That's indeed a good way to explain the utility driven nature of Go. I've been predominantly using OOP languages bef

>Golang was designed for getting shit done That's indeed a good way to explain the utility driven nature of Go. I've been predominantly using OOP languages before and Go's deliberate lack of OOP features was although uncomfortable at first, the advantages of getting things done fast far outweighed it later when I released production applications with it. >For me, Golang is like Python but with static typing and high performance. Fast to implement, easy to read, and focused on getting code out the door. I was tired of adding disclaimer when teaching Python, that when you want to extract performance out of it you should also learn 'C/C++'. Go serves as a perfect replacement to Python where performance is a necessity, I don't see where that would be false in a production environment where 'code performance == capital efficiency'.