This document contains my personal list of idioms, patterns, and best practices for Go. Some of these are my own, many are not, but this is an inherently subjective list. Error wrapping ... Prefer %q over %s If you're interpolating text that my include whitespace, prefer %q over %s because it removes ambiguity for the reader. Bad:

This document describes the primitives provided by FTL. These primitives can be composed Verbs, sources, and sinks These are the function primitives of FTL. Verbs Verbs take a single value and return a single value or an error. F(X) -> Y

Some ideas around what a proto4 might look like. This is just speculation/fun. Non-goal: This shouldn't be called proto4 😜 Non-goal: Source compatibility with proto2/3 (though perhaps offer a way to convert to/from .proto?) Goal: wire compatibility. Goal: remove the legacy limitations of protos (this is a terrible article but it has some valid points). Goal: improve language ergonomics where possible