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
1/4 I wonder if there's a case for a language enhancement here: JSON object/array literals. const store = JSON{ "answer": 42 }; Only JSON is allowed within JSON{...}. (And JSON[...] for arrays.) Vs. doing this today: const store = JSON.parse(`{ "answer": 42 }`);
I think there are more concerns here than just parsing overhead.
1)The recommendation moves most parsing of the literal from “parse-time” to “execution time”. This could be significant to implementations and apps (eg @moddabletech ) where “parse-time” is pre-deployment.
1/
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.