EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·9d ago·5 min read
Go JSON v2 Migration: What Breaks in Go 1.27
TL;DR
Go 1.27 introduces a new JSON encoding engine, v2, which enhances error handling and enforces stricter JSON rules. While existing code remains compatible, developers must be aware of case sensitivity and duplicate key restrictions.
✦ Why It Matters
Review your JSON handling code to ensure compatibility with Go 1.27's new v2 engine.
Key Takeaways
- Update imports to encoding/json/v2 for new features.
- Check for case sensitivity in field names.
- Handle potential changes in error messages.
- Test JSON handling with the new v2 engine.
Full Summary
With the release of Go 1.27, the standard library's encoding/json package is now built on the v2 engine, which includes compatibility options to maintain existing output. However, developers should note that error messages may change, and when using the new import path encoding/json/v2, field names will be case-sensitive, and duplicate keys will be rejected.
Additionally, the time.Duration type is affected by these changes. The release notes highlight two new packages and the transition to the v2 engine, which was implemented to improve JSON handling.
As of October 2026, the current version is Go 1.27.1, and benchmarks indicate that the new engine performs well under the GOEXPERIMENT=nojsonv2 setting. These changes aim to enhance the reliability and predictability of JSON processing in Go applications.