News for hackers. Stuff that matters.
Re:The Cost of JavaScript in 2019 by gmueckl on Sunday June 30, 2019 @12:59PM (#20319135)
The Json version only requires the full, complex JS parser to find the end of the string parameter. The string itself is then passed to a specialized Json parser that is faster because the language is a lot simpler and it has to check less possibilities at each point.

Apparently this is faster than running the whole string through the full JS parser that has has to deal with all kinds of portential shenanigans in that block like references to variables instead of literals etc.

Re:The Cost of JavaScript in 2019 by vbezhenar on Sunday June 30, 2019 @04:27PM (#20320304)
But that only applies to the parsing step. With JSON.parse you will parse it every time the code executes, so if that code is in function, JavaScript probably will be better, because compiler can't just optimize out JSON.parse (because someone might redefine window.JSON object or redefine its parse property).
Re:The Cost of JavaScript in 2019 by hedora on Sunday June 30, 2019 @07:04PM (#20321133)
That’s why you should put all your json literals at the topmost scope in the file. After all, global variables are the best variables.

(Per the article’s advice, unless I’m missing something)