News for hackers. Stuff that matters.
Re:Why I no longer have an old-school cert on my HTTPS site by motorest on Saturday May 24, 2025 @12:32PM (#44082125)
> I feel like not understanding why JSON won out is being intentionally obtuse. JSON can easily be hand written, edited, and read for most data.

You are going way out of your way to try to come up with ways to rationalize why JSON was a success. The ugly truth is far simpler than what you're trying to sell: it was valid JavaScript. JavaScript WebApps could parse JSON with a call to eval(). No deserialization madness like XML, no need to import a parser. Just fetch a file, pass it to eval(), and you're done.

Re:Why I no longer have an old-school cert on my HTTPS site by amne on Saturday May 24, 2025 @02:40PM (#44082987)
it's in the name after all: [j]ava[s]cript [o]bject [n]otation
Re:Why I no longer have an old-school cert on my HTTPS site by jaapz on Saturday May 24, 2025 @05:36PM (#44083953)
But also, all the other reasons written by the person you replied to
Re:Why I no longer have an old-school cert on my HTTPS site by motorest on Sunday May 25, 2025 @01:28AM (#44085751)
> But also, all the other reasons written by the person you replied to

Not really. JSON's mass adoption is tied to JavaScript's mass adoption, where sheer convenience and practicality dictates it's whole history most of the current state. Sending JavaScript fragments from the backend is a technique that didn't really stopped being used just because someone rolled out a JSON parser.

I think some people feel compelled to retroactively make this whole thing more refined and elegant because for some the ugly truth is hard to swallow.

Re:Why I no longer have an old-school cert on my HTTPS site by nextaccountic on Sunday May 25, 2025 @12:13AM (#44085471)
In other words, the thing that made JSON initially succeed was also a giant security hole
Re:Why I no longer have an old-school cert on my HTTPS site by motorest on Sunday May 25, 2025 @01:32AM (#44085767)
> In other words, the thing that made JSON initially succeed was also a giant security hole

Perhaps, but it's not a major concern when you control both the JavaScript frontend and whatever backend it consumes. In fact, arguably this technique is still pretty much in use today with the way WebApps get a hold of CSRF tokens. In this scenario security is a lesser concern than, say, input validation.