Go turned 5 years old

In his post on the festive event, one of the creators of the language Andrew Gerrand recalls how these years went and how it was five years ago. This is how the official site looked like; Go authors themselves called it “system language”, each line of code had to be terminated with a semicolon, in order to build their applications, they had to write makefiles — and the future of the language was covered with darkness. Immediately after the release, the “language from Google” attracted wide attention, after which the main wave quickly subsided without seeing anything new in the language. The few who saw the future in language formed the “core” of its development team, and the first version of the language released in 2012 was a serious achievement, thanks to which hundreds of programmers decided to take part in the development of the language and the ecosystem around it.

In addition to the "festive" post, of interest is the published decoding of a recent speech by Brad Fitzpatrick about the present and the future of Go . Officially, Brad - the creator of memcached, OpenID and LiveJournal - is developing Camlistore , but along the way, he often has to look into the Go source and add the functionality necessary for Camlistore to the language libraries or fix bugs.

So, regarding the future language. Go 1.4 will include several new features and bugfixes, while laying the foundation for the low-latency garbage collector and the ability to run Go on mobile platforms. Version 1.4 has already been released in the first beta, the release will be released on December 1.
')
Shortly after its release in version 1.5, it is planned to implement a new concurrent garbage collector (concurrent GC), which will reduce the time for this operation, and will no longer stop the program in a few minutes by a few milliseconds. The expected release date is 1.5 - June 1, 2015, and the authors of the language are looking forward to the fact that, after its release, Go will be used to develop those kinds of applications that were not worth writing on it for certain reasons.

It’s still too early to think about Go 2.0, at least because the developers haven’t decided that it’s possible and necessary to break, so the second version isn’t even in the plans. Therefore, we will find out what will follow version 1.5 in the next 5 years - and a series of articles from well-known gophers will be published as a holiday gift on the Gopher Academy blog this month.