What if Google lays off the Go team? (Go Time #315)

In this week’s episode we’re talking about the news! In this laugh-filled episode, Kris is joined by Ian & Johnny to discuss the future of Go, both the Go team itself and iterations of packages within the standard library; Microsoft creating a Go blog & a Go fork; and SQLite and Go.

Join the discussion

Changelog++ members save 8 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

• FireHydrant – The alerting and on-call tool designed for humans, not systems. Signals puts teams at the center, giving you ultimate control over rules, policies, and schedules. No need to configure your services or do wonky work-arounds. Signals filters out the noise, alerting you only on what matters. Manage coverage requests and on-call notifications effortlessly within Slack. But here’s the game-changer…Signals natively integrates with FireHydrant’s full incident management suite, so as soon as you’re alerted you can seamlessly kickoff and manage your entire incident inside a single platform. Learn more or switch today at firehydrant.com/signals
• Speakeasy – Instantly create SDKs that make API integration easy for your users. Create your first SDK for free! today.
• Fly.io – The home of Changelog.com — Deploy your apps and databases close to your users. In minutes you can run your Ruby, Go, Node, Deno, Python, or Elixir app (and databases!) all over the world. No ops required. Learn more at fly.io/changelog and check out the speedrun in their docs.

Featuring:

• Kris Brandow – GitHub, X
• Ian Lopshire – GitHub, X
• Johnny Boursiquot – Website, GitHub, X

Show Notes:

• If Google decided to part with the core Go team, what would that mean for its future adoption?
• Microsoft now has a Go blog
• Evolving the Go Standard Library with math/rand/v2
• Redis re-implemented in Go with SQLite

Something missing or broken? PRs welcome!