in increasing order of Unicode pedantry: U+002D U+2014 U+2212 U+2010 U+2028
-
-
Yup, and fun fact: U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR are the only two code points allowed in JSON strings that are *not* allowed in JavaScript strings (since they end the line)—so using ‘eval()’ to parse JSON is not only unsafe, but also incorrect
2 replies 1 retweet 4 likes -
2 replies 0 retweets 9 likes -
Replying to @FakeUnicode
Nice! I’ll refile that one under “historical trivia” then
1 reply 0 retweets 3 likes
Replying to @whyevernotso @FakeUnicode
It also means that JSON.stringify can be used to create valid JS string literals without manual post-processing. 
12:50 AM - 28 Jul 2019
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.