Perf tip: if your web app ships large JSON-like configuration as JavaScript object literals, consider using JSON.parse instead. It’s much faster, especially for cold loads! https://v8.dev/blog/cost-of-javascript-2019#json …pic.twitter.com/p0WICUm7zx
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
It's not exactly double parsing. Scanning the JSON string in the parser is really fast and wont add much overhead to parsing JSON. The JSON parser is much better optimized to deal with plain objects since it's not ambiguous and simpler.
For 300kb JSON config in Chrome my numbers are: - 5.7ms for evaluating script with plain object (`var config = {...}`) - 11ms for evaluating script with serialized config (`var config = JSON.parse("...")`) Inspected in the "Performance" tab. Am I doing something wrong?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.