His full name is JavaScript Object Notation. He goes by Jason. Born in 2001, he's been silently running half your digital life ever since — inside your apps, your logins, your weather forecasts, and approximately every API on the internet. Nobody ever introduced you. That ends now.
His full name is JavaScript Object Notation. He goes by Jason. Just Jason.
Born: 2001, somewhere in a California startup
Occupation: Professional data courier
Known for: Being inside literally every app, website, and API on the internet
Pet peeve: Trailing commas
You've never formally met Jason JSON, but he's been in your life for years. He's in the weather app on your phone. He's in every time you hit "Log In" and a server checks your password. He's in the checkout flow when you buy something online. He's in your fitness tracker, your streaming service, your work Slack.
He's everywhere. And he's been doing this quietly, without credit, since 2001.
It's time for a proper introduction.
Jason's Origin Story
Jason didn't exactly choose this life. He was discovered — not invented — by a software engineer named Douglas Crockford, who noticed something interesting while staring at JavaScript code one day.
"There's already a perfectly good way to organize data in here," Crockford thought. "Someone just needs to point at it."
That someone was him. In 2001, Crockford gave the format a name (JavaScript Object Notation), built a website for it (json.org), and sent Jason out into the world.
For a few years, nobody really noticed. Jason did some small gigs. He waited.
Then, in December 2005, Yahoo! gave him his first real job — they started using JSON in their public web APIs. And that was that. Once Yahoo! vouched for him, the rest of the industry followed. By the time smartphones arrived and every app needed a fast, lightweight way to talk to a server, Jason was the obvious choice.
Today he's processed more data than probably any other format in history. He never brags about it. He just shows up, delivers the goods, and leaves.
Jason's Personality
People who've worked with Jason describe him as: efficient, predictable, and slightly uptight about punctuation.
He's not complicated. He's not trying to impress you. He does exactly what he says he'll do, every single time, as long as you follow his very short list of rules. Break one of those rules — just one — and he shuts down completely. No error message. No compromise. Just silence and a cryptic note that says Unexpected token.
He has some quirks:
He only uses double quotes. Always. He finds single quotes tacky and won't discuss it.
He hates trailing commas. With a passion. You know when you have a list of things and you leave a comma after the last item out of habit? Jason considers this a personal attack. Don't do it.
He doesn't do dates. He will not commit to a Date type. Not because he can't — because he won't. If you need a date, he'll accept it as a string ("2026-07-22T16:00:00Z") and move on. Don't push him on this.
He never comments. No, really — he genuinely cannot handle // comments or /* notes */. He finds them a distraction. He is a pure data man. If you want to leave notes for yourself in a config file, he suggests you find a different format.
He's case-sensitive. true is true. True is an error. TRUE is a personal insult. He's very particular.
What Jason Actually Does
Jason is a courier. His entire job is picking up structured information from one place and delivering it to another — fast, complete, and in exactly the shape it was handed to him.
When you open a weather app and it shows you the forecast, here's what just happened: your phone asked a server, "What's the weather like?" The server handed Jason a package, Jason crossed the internet in milliseconds, and he knocked on your phone's door. The app opened it. Rain tomorrow.
Every time you scroll through an app and new content loads? That's Jason. Every time you submit a form and the page updates without refreshing? Jason. Every webhook, every API call, every background data sync happening right now on your devices? Overwhelmingly, Jason.
He's not flashy about it. He doesn't add commentary. He just delivers.
The 6 Things Jason Is Good At
Jason is a specialist. He knows exactly six types of things, and he knows them very well.
Text ("strings") — Anything in double quotes. "Hello", "alice@example.com", "some long sentence about nothing". His bread and butter.
Numbers — 42, 3.14, -7, 1.5e10. He doesn't care if it's an integer or a decimal. It's all just a number to him. He does not do NaN or Infinity. Those aren't real numbers, in his opinion.
Objects — Groups of related things, wrapped in curly braces. {"name": "Alice", "age": 30}. This is where he really shines. Give him a curly-brace package and he'll carry it all day.
Arrays — Ordered lists, wrapped in square brackets. ["coffee", "more coffee", "water eventually"]. He's very good at lists.
Booleans — true or false. That's it. Not yes. Not 1. true or false, lowercase, final answer.
Null — Nothing. The deliberate, intentional absence of a value. Not zero. Not an empty string. null. It means "this field exists, but there's nothing here right now." It's a meaningful nothing.
That's his entire toolkit. Six things. He's mastered all of them.
Jason's Rules (Non-Negotiable)
Over the years, Jason has developed a short list of personal commandments. He calls them his rules. Everyone else calls them "the reason my API is broken."
- Double quotes, always. Keys AND values. No single quotes. Ever.
- Commas between things, never after the last thing. He cannot be clearer on this.
- Colon between a key and its value.
"name": "Alice". Not an equals sign. A colon. - `true`, `false`, `null` are lowercase. This is not up for discussion.
- No comments. He is a data format, not a diary.
- Every opening bracket gets a closing bracket.
{gets}.[gets]. Mix them up and he's gone.
Jason vs. XML — The Rivalry
Before Jason came along, there was someone else doing his job. An older, more complicated fellow named XML.
XML was very thorough. Very detailed. Very into using opening AND closing tags for literally everything:
`xml
<user>
<name>Alice</name>
<age>30</age>
</user>
`
Jason's version of the same thing:
`json
{"name": "Alice", "age": 30}
`
People started to notice the difference.
XML had been around since 1998 and had built up quite a reputation for being the "right" way to move data around. But he was also exhausting. Developers had to write twice the characters to say the same thing. Parsing him required separate libraries. He came with a whole ecosystem of complexity that nobody had really asked for.
Jason was just... easier. He mapped directly onto the way programmers were already thinking. He was smaller, faster, and you could actually read him without a headache.
A 2012 study at Montana State University put them both through a stress test — processing one million objects each. Jason finished in 78 seconds. XML took 4,546 seconds. That's 58 times slower.
XML never really recovered from that. He still works in some legacy enterprise systems and complex document formats, and good for him. But for APIs — the job Jason was born for — it's been Jason's world for over a decade.
Where You've Already Met Jason
You've definitely encountered Jason before, even if you didn't know his name. He looks like this:
`json
{
"name": "The Octocat",
"company": "GitHub",
"location": "San Francisco, CA",
"email": null,
"followers": 20000,
"created_at": "2011-01-25T18:44:36Z"
}
`
That's a real response from the GitHub API when you look up a user. Jason picked that up from GitHub's server and delivered it — strings, numbers, a null (no email on file), a date as a string — wrapped up neatly, ready to use.
You've met him in:
- Every REST API response you've ever received
- Every
package.jsonfile in a JavaScript project - VS Code's settings file (
settings.json) - Your browser's local storage
- App config files across virtually every platform
- Database exports, log files, webhook payloads
He gets around.
Frequently Asked Questions (Answered as Jason Would)
Is Jason a programmer?
No. He cannot write code. He cannot run code. He cannot store code. He is a data format. If you are trying to put a function inside him, you have fundamentally misunderstood the relationship.
Can Jason take notes?
No. He does not do comments. He has said this many times.
Does Jason work with every programming language?
Yes. JavaScript, Python, Java, Go, PHP, Ruby, Swift, Rust, and basically any language with an HTTP library. He was always there. Now he works for everyone.
Is Jason the same as a JavaScript object?
Similar vibes, different personalities. A JavaScript object is more relaxed — single quotes, trailing commas, functions, whatever. Jason has standards. Use JSON.stringify() to convert a JavaScript object to something Jason will accept, and JSON.parse() to convert Jason's output back into a JavaScript object.
Is Jason secure?
Yes, as long as you use JSON.parse() to read him. There was a period when people used a JavaScript function called eval() instead. This was a mistake — eval() executes anything it reads, which is dangerous. Jason does not endorse eval().
The Bottom Line
Jason JSON is 25 years old, works harder than almost anyone on the internet, and asks for very little in return. Follow his six rules. Use double quotes. Don't leave trailing commas.
He will be there every time you open an app, check a price, load a page, or send a message. Silent, fast, and carrying exactly what you asked for.
You probably won't notice him. That's how he likes it.