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
I think this is different from what Andrew is proposing: Andrew is proposing the src/ files link back to docs, which I agree would be cool. It might increase the code size of our static doc pages even more, though.
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 took your suggestion and ran with it. So far total gzipped bytes for all std lib docs files is 400KB. That's main.js, data.js, index.html, no other files needed. Source listings not done yet, plan to keep that as separate .html pages.https://twitter.com/andy_kelley/status/1181423345759375360 …
Awesome. I still believe that a data file and a client side app would be way way smaller than our current piles of HTML, but haven’t been able to build something real enough to prove it. Might be interesting to compare what you have to a no-JS version...
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
