Then tell them to write all their code in Brainfuck if it's that easy. In fact, tell them to write a brainfuck transpiler in brainfuck to transpile go lang to

Then tell them to write all their code in Brainfuck if it's that easy. In fact, tell them to write a brainfuck transpiler in brainfuck to transpile go lang to brainfuck to make it easier for you communicate with their native tongue directly. https://stackoverflow.com/questions/16836860/how-does-the-brainfuck-hello-world-actually-work https://stackoverflow.com/questions/16836860/how-does-the-br... But honestly if you're a professional programmer, you should constantly be asking yourself how do I reduce complexity for others first, not myself. And that's where golang gets it wrong. Golang asks very specifically first and foremost how do they get their compiler right -- even if it comes at the potential expense of the users. I mean golang is not brainfuck by any margin, and it is reasonable for what it tries to do. But, in my experience, if you're writing code longer than a page, golang is probably the wrong language.