You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
At what point to we just accept that our docs need to ship ~2.6TB of javascript and embrace it?
TBH I'm surprised we're still shipping the search index as JS literals. Switching from JSON to any binary format would probably substantially improve both parse times and file sizes
Yeah, I just did the first implementation of dumping the semantic analysis results to a pretty compact JSON file (it's far from complete info still), and for the std lib it's already 903KB. Even a simple piping through gzip brings it down to 1KB (!)
I'm no compression expert but I'm pretty sure 900:1 ratio is inefficient data storage
is there a binary format we can parse from vanilla JS? rustdoc is designed to be run as a static site generator, so we'd need to be able to parse/load the search index 100% offline
There's a Rust generator for full text indices compatible with elasticlunr, which is AFAIK not binary, but also not token storage.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
