Lies we tell ourselves to keep using Golang
I didn&#x27;t care in the last post and I don&#x27;t care about this one either. I care about my productivity, I care about my team&#x27;s productivity, and I care about getting stuff shipped. Those are the things I care about, and go works great for that. If you care about those things too, and you&#x27;re using go, you shouldn&#x27;t stop using go.<p>My whole career people have been telling me to stop using languages or tools I&#x27;ve been productive with. I&#x27;ve built successful companies where everything was written in python, the whole time people on HN telling me how I was using a lowly language because of things like whitespace significance or strings that were not unicode by default.<p>If you care about other stuff, fine. If you don&#x27;t think go works for you, don&#x27;t use go. Just stop telling people who are using go (and other productive languages) to stop using them because of obscure language design issues or obscure API choices that people rarely encounter day to day. That isn&#x27;t what matters to most people, and it&#x27;s actually bad advice.<p>The problem is that there are a ton of less experienced people reading stuff on HN (just as I once was) who will take this to heart but have nothing actionable to gain from it, except to think they&#x27;re a bad developer using a bad language. They aren&#x27;t, and they&#x27;re not.