BitBench – Visually dissect and analyze bit strings
github.com
github.com
This way you would be able to interactively see how unicode and different runes are represented in bytes, how they are also abstractly represented in your programming language array data structure, and how finally they are stored on your little-endian system.
I wish golang had never appropriated the term "rune". Runes are Viking writing. Unicode has Code Points, not runes!
In addition, Rune refers to a specific implementation of the code point. As far as I am aware, UTF-8 doesn't define a code point as being uint32, rather it just defines it as a point within the code space (which is defined to be at least a certain size), a code point could be implemented in any number of ways internally. When talking about implementation details, a Rune is defined as a uint32, which is analogous (for implementation purposes) as a code point.
That is to say, a Rune is a manifestation of a code point, but a code point need not always map to that internally. This is like complaining over using "int" instead of "uint32_t" (I'm sure someone else can think of a better example, actually).
rune.c:2: "The authors of this software are Rob Pike and Ken Thompson."
https://github.com/9fans/plan9port/blob/master/src/lib9/utf/...
[0] https://sites.google.com/site/xxcantorxdustxx/