I’d argue JSON and whatever that mess of a JSON implementation in JS are are two different things.
“What possibly can be so difficult about JSON?” After the video I cried in the corner.
I feel like half of this video is inspired by me pointing out why I use null in JS.
This is more about how Javascript handles JSON than JSON itself. Most of these were about how the JSON library handles undefined/null/edge cases that don't exist in other languages, and depend on the library you use. All this to say, I did terribly.
"JavaScript, 💩, an embarrassing toy language used exclusively to build things it's not supposed to."
The single fact that JSON has his own native class on JavaScript with just two methods should have already told you that something was fishy over there
Tell me... how many did you ackshually get wrong? DONT LIE
i laughed out loud when you said "don't worry it's not going to get any easier"!
I absolutely loved this video and hated it so much at the same time thanks for this awesome content
2:52 YouTube hand-picked the exact video that I watched two minutes ago and that led me to watch this video. Are they dumb or do they want me to enter an infinite loop?
That’s more about the absurdity of JavaScript and it’s JSON module and less about JSON.
The dude has great comedic delivery. The video had me rolling from the getgo.
I hate this game that we're playing
Software development in 2024: watch other devs coding while copilot is responding
Fun fact the JSON global object with parse and stringify was once a library by the Chuck Norris of Javascript, Doug. Browsers just made it native. At the time, it was a security concern that some devs were just doing eval()!
My morale is now undefined.
Wait a minute BIG SAUCE, that property is private, you little mischief
Are those behaviors in the spec? Meaning other json parsers should implement them? Sounds more like a JavaScript WAT instead of JSON.
More arguments about JS being horrible than it being about json
@tesla1772