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
This claim seems insufficiently justified to me: The JSON.parse version still needs to parse the string literal. That may be fast, but it’s not guaranteed to be, and it’s not free.
Could you elaborate on what‘s missing? The JavaScript string literal grammar is much simpler compared to the JavaScript object literal grammar, per spec. That indeed doesn’t mean string parsing is “free”, but it’s definitely cheaper.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.