Talks to Watch

Characters, Symbols and the Unicode Miracle - Computerphile

2.1M views · Sep 20, 2013 · 9:37 · 4 HN recommenders · 6 mentions · discussed 2014–2025

Tom Scott explains for Computerphile how Unicode and UTF-8 grew out of messy older character encodings to become the web's standard. It covers why the design works and how it handles worldwide text.

Why Hacker News points people here: HN treats it as the go-to short explanation of UTF-8, praised for making the topic stick.

“a wonderful, terse, very informative video describing how utf-8 encoding works and why”HN comment, 2020

What Hacker News said 6

Strongly recommendsdoucheApr 2016

“That is one of my all-time favorite youtube videos”

Illustrates hidden complexity in software to non-technical people.

Full comment

That is one of my all-time favorite youtube videos... This one, and a similar one on unicode[1], are my goto exhibits when I need to illustrate to a non-technical family member how much background complexity is involved in software [1] this video

in “Falsehoods programmers believe about time and time zones” · view on HN
Strongly recommendswcarssAug 2020

“a wonderful, terse, very informative video describing how utf-8 encoding works and why”

Terse explanation of how UTF-8 works and why.

Full comment

Something complementary -- because this article just takes a moment to talk about the different encoding schemes -- a wonderful, terse, very informative video describing how utf-8 encoding works and why (with a little history) by Tom Scott/Computerphile: this video

in “Unicode in five minutes (2013)” · view on HN
Strongly recommendsjanvdbergJan 2024

“Tom is why I understand UTF-8”

Tom Scott's enthusiastic explanation made UTF-8 stick.

Full comment

Tom is why I understand UTF-8 [1]. And it is not so much WHAT he explained but HOW he explained it, what really made it stick. It was his sheer unbridled genuine enthusiasm that put him on the map for me. One of the best to do it. [1] this video

in “Tom Scott: After ten years, it's time to stop making videos [video]” · view on HN
RecommendsmcphilipMar 2014

“I like Computerphile's video on the evolution of character encoding and why UTF was developed.”

Evolution of character encoding and why UTF was developed.

Full comment

I love Numberphile too and recently stumbled on Computerphile. The style is the same for both shows -- a passionate person explaining something reasonably complex. For instance, I like Computerphile's video on the evolution of character encoding and why UTF was developed. this video

in “LHC Physics Center bans Powerpoint, switches to whiteboard-only forums” · view on HN
Cites itjanvdbergApr 2021

“More or less same the story but in an explainer video”

Explainer video covering the same UTF-8 story.

Full comment

More or less same the story but in an explainer video: 'Characters, Symbols and the Unicode Miracle - Computerphile' this video

in “The history of UTF-8 as told by Rob Pike (2003)” · view on HN
Cites itRendelloJun 2025
Full comment

That tripped me up too. The Unicode Core spec is quite good at explaining things and introduces some terminology you don't really hear outside the document. Chapter 2, General Structure , is worth reading in its entirety. I've linked some bits that might help: > *2.2.3 Characters, Not Glyphs* > The Unicode Standard draws a distinction between characters and glyphs. Characters are the abstract representations of the smallest components of written language that have semantic value. They represent primarily, but not exclusively, the letters, punctuation, and other signs that constitute natural language text and technical notation. [...] Letters in different scripts, even when they correspond either semantically or graphically, are represented in Unicode by distinct characters. > Characters are represented by code points that reside only in a memory representation, as strings in memory, on disk, or in data transmission. The Unicode Standard deals only with character codes. > *2.4 Code Points and Characters* > The range of integers used to code the abstract characters is called the codespace. A particular integer in this set is called a code point. When an abstract character is mapped or assigned to a particular code point in the codespace, it is then referred to as an encoded character. > *2.5 Encoding Forms* This deals with UTF-{8,16,32}, which is a tricky bit and tripped me up for a long time. If the document is too dense here, there's a lot of supplementary material online exp

in “Ask HN: What are your Unicode woes?” · view on HN