Perspectives of the go language for the programmer

The article was written based on one not very pleasant conversation on the last IT global mitap in St. Petersburg.

I like the go language. It is very simple, it is easy to learn (I checked it in practice - it can really be mastered in one weekend). Gorutiny, http-server and much more right out of the box, ease of reading someone else's code. The Evangelicals of the language claim that the language was specifically created so that any newcomer could quickly go into the project and begin to figure out the code. Those. everything is made as simple as possible.

Accordingly, for business this language is also very good - you take everyone in a row, roughly speaking, schoolchildren and students, you teach quite a bit, and voila, you have a team. Try this with some c ++.
')
At the mitap, there was an expression “pick meat” that would write code. This incidentally said the evangelist golang, who struggled to persuade everyone to go to go.

Stop!
He said ... "meat" ??

He said so, I did not hear!

And here, as they say, I was covered. Do I want to make go my main language of development? Those. become “meat”?

What are the perspectives of go language in terms of career growth? If the language has an extremely low threshold of entry, then sooner or later all newcomers will be there, the supply will exceed the demand, and they can be taken as a ruble for a dozen.

Well, let's say, money is not the most important thing.

But even here go with its hyper simplicity will probably never be something exciting. What is the challenge (except how to learn a new language over the weekend)? Where is architecture, where are puzzle patterns about which you can argue with your colleagues?

Well, that is, the benefits of go language for business are clear, but what about a programmer? What is the motivation for the future?

In fact, it strongly resembles the development of php in zero years. Then the language was extremely simple, and due to this, absolutely everything began to be written on it. Each student could throw a buggy saytik for a penny, not bothering with the PLO, patterns, and indeed with nothing.

But! Php has since become very complicated, improved, now it is a full-fledged language with a developed infrastructure and, in fact, already a rather big entry threshold. Circuits, generators, full-fledged OOP, traits, optionally strict type checking, etc. were stuffed into the language. Now, in order to find a normal php job, you need to know at least one rail-like framework.

But go - not php. He thought of a simple by design, and not because it happened. And they will never go to complication.

It is clear that knowledge of a language is only a small fraction of the work of a programmer. You also need to understand the senseless murmur of the manager and turn it into a logical code. You also need to be able to work with the database, be able to interact with colleagues in a team and thousands more of these things. But other things being equal, the go language, it turns out, is probably not as interesting as the others.

If you already look at fashionable languages ​​for the future, then perhaps you should pay attention to rust or something like that. There, without understanding the concept of ownership, you cannot even compile a helloworld-like program. Here is the challenge!

To summarize.
Despite the fact that I wrote above, I still like the language)
In general, for the time being I have decided for myself that I will probably use the go language for some things (for example, if I start stirring up some startup), but I will probably never make it my main one, i.e. first line in a hypothetical future summary.

Actually, it is very interesting to know the opinion of those who constantly write on go, share pliz what motivates you for the future. This is the rare case when you really want to change your point of view on the opposite!