In my opinion, Go provides excellent support for concurrent work, not only due to goroutines but also because of the language’s ecosystem. A great example of this is the sync package, which helps synchronize concurrent routines. In this post, we’ll dive into everything this package has to offer.

yzma lets you use Go to perform local inference with Vision Language Models (VLMs), Large Language Models (LLMs), Small Language Models (SLMs), and Tiny Language Models (TLMs) by using the llama.cpp libraries all running on your own hardware.

MoniGo is a performance monitoring library for Go applications. It provides real-time insights into application performance with an intuitive user interface, enabling developers to track and optimize both service-level and function-level metrics.

Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the standard for content-addressing on the Web, interoperable with HTTP. Thus powered by future-proof data models and the libp2p for network communication. Kubo is written in Go.

Flint is a modern, self-contained KVM management tool built for developers, sysadmins, and home labs who want zero bloat and maximum efficiency. It was built in a few hours out of a sudden urge for something better.

Runtime Radar is an open-source solution for monitoring runtime security events and responding to incindents in containerized environments.

Go 1.25 includes a new experimental garbage collector called Green Tea, available by setting GOEXPERIMENT=greenteagc at build time. Many workloads spend around 10% less time in the garbage collector, but some workloads see a reduction of up to 40%!

It’s production-ready and already in use at Google, so we encourage you to try it out. We know some workloads don’t benefit as much, or even at all, so your feedback is crucial to helping us move forward. Based on the data we have now, we plan to make it the default in Go 1.26.

Go is released every six months. Each release cycle is broken down into a development phase lasting about 4 months, followed by a 3-month period of testing and polishing called the release freeze. If everything goes well, work on the next release begins before the previous release has shipped, resulting in an overlap of about a month.

TL;DR Meridian uses Go generics to encode timezones directly into the type system (et.Time, pt.Time, etc.), catching timezone bugs at compile time instead of production.