Why Go gets criticized so much
I think there is a better explanation for why people dislike Go. All programming languages currently used for the web have gigantic downsides. They&#x27;re slow. They have terrible package management. They have poor standard libraries. They have no static typing. They have no visual debuggers. They have no good IDE support. They don&#x27;t integrate well with frontend code. Some programming languages are more flawed than others, and no programming language fails on every front, but they&#x27;re all pretty objectively terrible.<p>Then Google announces Go. A cross-platform systems programming languages for high quality web services. That sounds great! I can&#x27;t wait to see what Google came up with.<p>So when people saw Go disappointment set in. It has some great properties, but the language is not expressive. So Go web frameworks (like Revel) generate Go code at compile time to get the dynamic parts working. Just like we did in the 70s to work around C&#x27;s shortcomings. Want a container for a specific type? Code generation! It&#x27;s so clumsy. The lack of exceptions makes writing correct code really tedious. A web service is not a device driver where every edge case has to be carefully considered. Bailing out with an exception is fine. Go disagrees.<p>I think the disappointment in what Go <i>could have been</i> explains the vocal dislike. There are only a few companies in the world that can create a new programming language and ensure it becomes popular. Don&#x27;t get me wrong. Go isn&#x27;t a bad language. It&#x27;s just not the language that will push the web forward, and Google was in a unique position to create a programming language that would.