This isn't quite right. In invalid UTF8, a continuation byte can also emit a replacement char if it's the start of the byte sequence. Eg, `0b01100001 0b10000000 0b01100001` outputs 3 chars: a�a. Whether you're at the beginning of an output char depends on the last 1-3 bytes.
Any chance it was https://pomb.us/build-your-own-react/? You can't really have hooks without building an entire framework, because the framework has to have the preserve the execution context between renderings.
Our initial development cycles were dedicated on getting Next working. But we absolutely plan on expanding the to support generic bundling and will include that in the docs.
Google Docs will eventually be overloaded with all the people accessing the doc. Linking to the [Preview] version helps, because it doesn't have to load the multi-user edit interface.
rawgit.com is sunsetted[1], so this URL may die any day now. It's simply a proxy server for content hosted on GitHub. In this case, the real source is https://gist.github.com/darcyparker/1886716, and it's displayable (officially) at [2].
The post isn't super clear, but I think they're describing base62 here. It says base62 later in text when talking about the checksum, and the "Our implementation for OAuth access tokens are now 178" section uses `a-zA-Z0-9` which is base62.
I don’t really follow what’s going on with larger Google. AMP team specifically has a collection of older phones that we test on to remember that we’re making decisions for low end devices common in other parts of the world.
> truncate a string without splitting a codepoint in O(1) is still useful
Agreed!