PROGRAMMING
Why Golang Is Bad for Smart Programmers
An honest review of why Golang may be bad for experienced developers
--
In recent months I use Go for the implementation of Proof of Concept in my leisure time, partly to study of Go programming language itself. Such “Hello World!” programs themselves are elementary and not the purpose of this article, but the experience of using Go itself deserves a few words about it.
Go promises to be the mainstream language for scalable severe code. The language was created by Google, in which it is actively used. To sum up, I honestly think that the design of Go is bad for smart programmers.
Golang — Designed for weak programmers?
Go is very easy to learn, so simple that it took me one evening to introduce it, and then I could write code productively. The book on which I have studied is called Go is An Introduction to Programming in Go. The book, like the Go source code itself, is easy to read, has good code examples, and contains about 150 pages that you can read at a time. This simplicity is refreshing at first, especially in a programming world full of overcomplicated technologies. But in the end, sooner or later, the thought arises: “Is this really so?”
Google claims that the simplicity of Go is a compelling trait, and the language is designed for maximum productivity in large teams, but I doubt it. There are features that are either lacking or overly detailed. And all due to the lack of trust in the developers, with the assumption that they are not able to do something right. This pursuit of simplicity was a conscious decision of the developers of the language. In order to fully understand what it was for, we must understand the motivation of the developers and what they were striving for in Go.
So why was it made so simple? Here are a couple of quotes from Rob Pike, who is one of the sponsors of Go language:
The key point here is…
