Happy birthday, go!
On Sunday, we celebrated the fifteenth anniversary of the GO Open Source version!
Many have changed since then The anniversary of 10 yearsBoth in going and in the world. In other ways, much remained as it is: Go is still committed to stability, safety, and the support of software engineering and production on a large scale.
And going strong! The GO user base has multiplied more than three times in the past five years, making it one of the fastest growing languages. Since its inception only fifteen years ago, Go is the 10 best language and modern cloud language.
With publications Go 1.22 in February and Go 1.23 in AugustIt was general for Episodes. Go 1.22 The variables offered by for Rings Determine the range for each repetitionInstead of each episode, the processing of long -term “Gotcha” language. More than ten years ago, before the Go 1 version, the Go team made decisions about many language details; Among them for The episodes must create a new loop variable in each repetition. It is tangible, that the discussion was very short and unique.
Rob Pike closed it in the real Rob Pike style with one word: “Stet” (Leave it). And so it was. Although it seems that it appears to be an apparently important at the time, years of experience in production has highlighted the effects of this decision. But at the time, we also built strong tools to understand the effects of changes that must be done-not in particular, analysis and testing at the ecosystem level via the entire Google Code base-work operations with society and get comments. After comprehensive tests, analysis, and community discussion, we put the change, accompanied by a retail anatomy to help developers in determining the widely affected code.
Change to for The episodes were part of the course of measured changes for five years. It was not possible without Language corresponding forward It was presented at GO 1.21. This, in turn, is based on the basis set by GO stereotypes, which were presented at GO 1.14 four and a half years ago.
Go 1.23 more on this change to enter the recurrents Episodes for the extent of knowledge by the user. Along with limestone drugs – they are presented at GO 1.18, just two and a half years ago! This creates a strong and comfortable basis for custom groups and many other programming patterns.
These versions also brought many improvements in the willingness of production, including The long -awaited improvements for the HTTP router for the standard library, Total reform of the effects of implementationAnd Random stronger For all Go apps. In addition, our introduction The first V2’s standard package It creates a template for the development and modernization of the future library.
Over the past year, we were brought up with caution Subscribe to remote measurement Go to tools. This system will give GO developers to make better decisions, while staying completely open and unknown. Go Telemetry for the first time in GOPLS, GO server, has already led to a set of improvements. This effort paves the way to make programming in a better experience for everyone.
We look forward, we are developing better to benefit from the capabilities of current and future devices.
The devices have changed a lot in the past 15 years. In order to ensure that GO continues to support the burdens of high -performance production work and its widespread measuring the next 15 years old, we need to adapt to large advanced instructions groups, and the increasing importance of the region in increasingly uniform hierarchy. Some of these improvements will be transparent. Going 1.24 will be completely new map Implementation under the hood is more efficient on modern central treatment units. We lead to preliminary models of the new garbage collection algorithms designed about the capabilities and restrictions of modern devices.
Some improvements in the form of new application programming and tools will be, so that developers can better benefit from modern devices. We are looking at how to support the latest instructions for veil and matrix devices, and multiple ways that applications can build in the CPU and Memory. A basic principle that directs our efforts Authorship improvementThe effect of improvement on the base of the code should be as translated as possible, ensuring that the ease of development is not exposed through the rest of the code code base.
We continue to ensure that the Go’s standard library is virtual and safe according to the design. This includes continuous efforts to integrate the original built -in support for the FIPS, so that FIPS Crypto is just a far -fly knowledge of the applications that need it. Moreover, we are developing the standard library packages of GO where we can, and follow an example math/rand/v2Looking at the place where new application programming interfaces can enhance the ease of writing the safe and safe Go.
We are working to better achieve artificial intelligence – and Amnesty International – by enhancing the GO capabilities in the infrastructure of applications and applications and assisting developers. Go is a great language for building production systems, and we want to be a great language for Production Amnesty International Systemsalso. Dependence on GO has made cloud infrastructure language a natural option for LLM infrastructure as well. For artificial intelligence applications, we will continue to build first -class support for GO in popular SDKS, including Langchaningo and Genkit. Since its inception, Go aims to improve the process of comprehensive software engineering, so it is normal to look at providing the latest tools and technologies of artificial intelligence to reduce the developer’s ingredient, and leave more time for fun things-already programming!
Thank you
All this is only possible because of the amazing Goo share and the prosperous society. Fifteen years ago, we could only dream about the success that became Go and the community that developed around Go. Thanks to everyone who played a big and small role. We wish you all the best next year.
Credits: Austin Clemens, for the Go team
Photography by Jason Lyong on the non -earthquake
This article is available on
