4 ms·
> Second, JSON always had a parser in JS, so I don't know where that eval nonsense is coming from. Firstly, it sounds like XML ran over your dog or something.
by fmakunbound 6y ago
> Second, JSON always had a parser in JS, so I don't know where that eval nonsense is coming from.
Firstly, it sounds like XML ran over your dog or something. Sorry to hear about that. It wasn’t particularly hard to use at all, and if you’re dealing with the possibility of emojis in your JSON UUIDs in 2021, one might even say it’s easier to use.
If you’re referring to JSON.parse() in “had a parser” above, then you have a temporal problem. Regarding eval(), it’s suggested right in the original RFC for JSON. Check it out. Web developers at the time were following that advice.
- BlueTemplar 6y agoAnother issue is that due to their age, a lot of XML tools ignore the existence of Unicode (or UTF-8).