News for hackers. Stuff that matters.
Re:The Cost of JavaScript in 2019 by baddox on Sunday June 30, 2019 @02:43PM (#20319718)
The runtime can't know whether it's parsing a plain old JSON-compatible object literal until it, well, parses it.
Re:The Cost of JavaScript in 2019 by epicureanideal on Sunday June 30, 2019 @04:21PM (#20320273)
Sounds like some sort of compiler hint like ‘expect json’ or ‘use json’ right above a json literal would be useful. Assuming it matters enough to be worth it.
Re:The Cost of JavaScript in 2019 by vbezhenar on Sunday June 30, 2019 @04:23PM (#20320282)
JSON.parse sounds like a good compiler hint :)
Re:The Cost of JavaScript in 2019 by pbhjpbhj on Sunday June 30, 2019 @02:52PM (#20319765)
IANAProgrammer but couldn't it do like try..catch and assume it's JSON compatible and fall back to the [much] slower method if the parse fails? Does that cost too much time/resources?
Re:The Cost of JavaScript in 2019 by baddox on Sunday June 30, 2019 @05:04PM (#20320506)
Isn’t that effectively what a backtracking parser does? My naive guess is that’s already roughly how the JS parser works, and that process is what makes it slower than the simpler JSON parser.
Re:The Cost of JavaScript in 2019 by daleharvey on Sunday June 30, 2019 @03:10PM (#20319876)
That would make all JavaScript that has non JSON object literals (most JS code) slower
Re:The Cost of JavaScript in 2019 by pbhjpbhj on Sunday June 30, 2019 @03:33PM (#20320011)
How much slower?

We already established it's far slower parsing js; in most cases JSON parsing would fail - IIRC - on the first character ^[^{] ... so would it be worth being slower by the time it takes to check the first character, and then only JavaScript that started with { would be slower. Which I guess is virtually none.

I suppose those sorts of questions are part of what makes language design interesting.