Go 1.26 Release Party

Name: Go 1.26 Release Party
Uploaded: 2026-02-19T17:55:17.000Z
Duration: 1 h 38 min 49 s
Channel: JetBrains

JetBrainsFebruary 19, 20261h 38m

Topics36

Welcome and Introduction0:12 Speaker Introductions1:30 Favorite Features Discussion3:02 Housekeeping and Release Context4:32 New Built-in Expression9:01 Error Type Checking12:30 Garbage Collection Changes17:31 Go Fix Command24:32 Questions and Discussion30:00 Vectorized Operations Feedback35:18 Secret Mode Feature36:01 Goroutine Leak Detection42:00 Runtime Metrics Enhancement47:32 Iterator Expansion in Standard Library51:02 Slog Multi-Handler54:00 Bytes.Buffer Peek Method57:30 Error Formatting Performance1:00:30 Secret Mode Memory Behavior Clarification1:04:01 Go 1.26 Migration Demonstration1:07:30 Syntax Analysis for Updates1:11:06 Selective Fix Application1:12:31 Error Handling Modernization1:13:31 Go Fix Command Usage1:14:02 Go Fix Reliability1:16:02 Benchmark Considerations1:17:00 Benchmark Execution1:19:33 Log Handling for Simple Applications1:20:00 Log Flight Recorder Implementation1:21:31 Multi-Handler Setup1:23:00 Live Templates for Development1:25:04 Application Configuration1:27:32 AI Delegation Strategy1:28:31 AI Prompt Engineering1:29:30 Go 1.26 AI Compatibility1:31:01 Claude Code Limitations and Solutions1:33:30 Plugin-Enhanced AI Output1:35:50

In a Nutshell

Go 1.26 introduces major features including a new built-in expression that allocates and initializes in one step, `errors.AsType[T]` for compile-time safe error type checking, and the "green tea" garbage collector that reduces CPU cache misses for 5%+ gains on small-object workloads. The release adds production-ready goroutine leak detection via `runtime/pprof`, `runtime/secret` for cryptographic memory clearing, `slog` multi-handlers, iterator methods across `reflect`, and `go fix` for automatic modernization. Performance improvements double I/O throughput, while new runtime metrics and `bytes.Buffer.Peek` enhance observability and buffer handling.

AI-Generated Notes

These notes were generated by AI and may contain inaccuracies.

The Go 1.26 live stream celebrates the release of the new version of the language. The moderator admits to knowing only how Go is spelled and will rely on two experts to carry the discussion. The audience is invited to share their favorite features from Go 1.26 in the chat.

Alex Hughes is a software engineer from Brazil working in leadership roles, participating in conferences and workshops, and writing books about Go. Anton works with Go both professionally and in his free time, preparing interactive tours for Go releases over the past few years.

Alex identifies type checking for errors as his favorite feature, noting Go now has an error as type concept. Anton highlights four features: goroutine leak detection (experimental), the new cmd capability in Go, performance improvements including I/O doubling in performance, and the ability to identify the cause of a signal cancellation for troubleshooting and debugging.

The release is referred to as Go 1.26. The stream is recorded and will be available on YouTube afterward. A giveaway includes a six-month extended GoLand trial using the code "go release party." GoLand 1.26 support was prepared in the latest version. Anton describes Go 1.26 as the biggest release seen, with the sheer number of features packed into it being astonishing.

The new built-in previously allocated a variable of a specific type and required separate assignment. In Go 1.26, new accepts any expression including specific values, structs, or function call results. The Go runtime allocates the variable, assigns the value, and returns a pointer. This is particularly useful for structs with optional fields used in JSON or protobuf serialization. Projects with helper functions like ptr can now delete these helpers and use the new built-in directly.

The errors.As function previously required declaring a target variable before calling, then checking a boolean result. The new errors.AsType generic function takes an error type as a generic parameter and the error value as a regular parameter, scoping variables to if branches. When checking multiple errors like operation errors, DNS errors, or other errors, each variable remains scoped to its branch. The construction resembles a switch statement for errors, which cannot use regular switch due to wrapping. Errors.AsType is more type-safe than errors.As since it checks at compile time whether the type implements the error interface. The function is faster, allocates less, and does not use the reflect package. The Go team recommends using errors.AsType instead of errors.As going forward.

Go has a single garbage collector that works well without configuration. The old collector was a mark-and-sweep implementation that jumped across heap memory regions, causing CPU cache misses where the CPU spent up to 35% of garbage collection time waiting for memory. The Go runtime allocator uses spans, which are linear 8-kilobyte blocks split into equal slots. The new "green tea" garbage collector works with spans so objects are located adjacent to each other, allowing the CPU to load chunks containing multiple objects. This reduces cache misses and improves efficiency. Average applications may see marginal improvements, but applications allocating many small objects may see approximately 5% reduction in overall CPU usage. The green tea collector is enabled by default and the old collector can be temporarily switched back, though this option will be removed in future releases.

Sign in to read the full notes

Get access to AI-generated notes, topic timestamps, and more.

Go 1.26 Release Party

Welcome and Introduction00:12

Speaker Introductions01:30

Favorite Features Discussion03:02

Housekeeping and Release Context04:32

New Built-in Expression09:01

Sign in to read the full notes