Three minutes isn't nearly long enough to talk about the
rune data type
in Go, but I tried anyway.
Here are some good resources related to character encoding and memory allocation:
Things I didn't cover:
bytealias an unsigned integer (
runealiases a signed integer (
int32)? Turns out if you ask that in the Go Google Group, they get a bit annoyed.
At about 2:10, I say,
When it gets more complicated is when you need to represent multi-characters [sic]. I misspoke, and meant to say multibyte characters.