Blog / Go Language Spec

Half way there

December 4, 2023

No live stream today. I’m still feeling a bit under the weather. Hopefully next week we’ll be back on schedule.

In January, I started this series on the Go spec, not having any idea if I'd have even 2 readers, or how long it would take to get through the whole spec.

This week we passed the half-way mark on that journey through the spec, and there are over 400 of you subscribed to this daily list. Thank you!

When I started the series, I had in the back of my mind that perhaps one day I would turn the series into a book. A sort of “Go Spec Study Bible”. I’m curious to know your thoughts, so I want to use this milestone to solicit your feedback. If you have a moment, would you hit reply, and let me know your thoughts?

  1. What have you learned during this series?
  2. How could the series be made more valuable to you?
  3. Would you find a this commentary on the Go spec valuable in book format?
  4. If so, would you be interested in receiving a free copy of the book, in exchange for providing your early feedback?

That’s it for now. Thanks for being part of this process!

Share this

Direct to your inbox, daily. I respect your privacy .

Unsure? Browse the archive .

Related Content

I'm looking for new clients

Could your project benefit from my expertise? I’ve had some availability open up in my schedule recently, so I’m announcing my new “Fractional Gopher” subscription service. I can help build your new features, pay down technical debt, audit your project’s code and architecture, or help in any number of ways. You’re already running my code in production. I’ve contributed to the Go standard library, as well as popular Go libraries such as echo, Logrus, and many others.

Dependency pinning

Today I want to share a trick I stumbled upon. It won’t matter to most of you. If it does matter to you, it will probably save you a bunch of headaches! First, some background. Have you ever had to use an outdated dependency for $REASONS? If not, you can skip today’s email, unless you’re just curious. One of my clients is still using MongoDB 3.2. MongoDB was EOLed more than a year before anyone had ever heard the term “COVID”.

Why is context.TODO not just a comment?

I’ve been on vacation for the last week, so haven’t written much. Let’s finally finish up the context package series with some reader feedback and questions! Joost Helberg wrote in with an interesting observation about context.TODO. In his own words: With regards to context.TODO, back in my early Go days, I thought the TODO was about the intent of this context. Like context.Background is for a background task and context.WithCancel for a job that can be canceled.

Get daily content like this in your inbox!

Subscribe