Lectures

We break down how the compiler directive //go:embed lets you “bake” files and entire folders into a Go binary at the go build stage. We discuss the key rule about package-level variables, choose the receiver type ( string, []byte, embed.FS), connect the import correctly ( import _ "embed" vs import "embed"), work carefully with paths, and build a mini example for the tasker help command without reading from disk.

We break down how to read embedded files from a binary via embed.FS and the shared interface fs.FS: why you should use functions from the io/fs package, how to diagnose “file not found” via fs.ReadDir, and why you should not blindly apply filepath.Join to paths inside embed.FS.

We break down how to organize embedded resources in Go using embed and the io/fs abstractions: why you need fs.Sub, how to “re-root” a file tree and expose only fs.FS, how to centralize resource access in an assets package, and why for paths inside fs.FS you must not blindly use filepath.Join (you need path.Join). At the end: wiring it into a CLI and common mistakes.

We break down practical scenarios for embed in Go: how to embed a help text into the binary and read it via fs.ReadFile, how to keep sample CSV/JSON as a “format example” and print it via a CLI command, and how to parse templates via template.ParseFS without string concatenation. Plus: a neat assets package with a single resource root ( fs.Sub) and a walkthrough of common mistakes.

We break down practical “rakes” (common pitfalls) of embedded resources in Go: how a path inside fs.FS differs from an OS path, why you must not build paths for embed.FS using filepath.Join, how to choose //go:embed patterns, how to inspect contents with fs.ReadDir, why you may want to “re-root” resources via fs.Sub, and what you pay for convenience: bigger binaries, full-file reads via fs.ReadFile, mandatory rebuilds, and no “secrecy” for embedded files.