JSON has been the web's data format for over two decades. While the core format stays stable, the ecosystem around it continues to evolve.
JSONC (JSON with Comments)
Already widely adopted in VS Code and many tools:
{
// This is a comment
"name": "My Project",
/* Multi-line
comments work too */
"version": "1.0.0"
}
Used in: tsconfig.json, VS Code settings, and increasingly in other tools.
JSON5 Format
A more human-friendly superset of JSON:
{
// Comments
name: 'Unquoted keys', // Single quotes OK
items: [1, 2, 3,], // Trailing commas OK
multiline: "Line 1\nLine 2", // Multiline strings
hex: 0xFF, // Hex numbers
inf: Infinity, // Special values
}
Typed JSON Proposals
Efforts to add type information to JSON:
{
"name": { "_type": "string", "value": "Alice" },
"birthday": { "_type": "date", "value": "1990-01-15" },
"balance": { "_type": "decimal", "value": "1234.56" }
}
JSON Schema Evolution
JSON Schema continues to advance:
Performance Trends
What Won't Change
The Verdict
JSON isn't going anywhere. New formats complement it rather than replace it. The most important trends are better tooling (validation, schemas) and performance (streaming, SIMD parsing).
Use our JSON tools — Formatter, Validator, Viewer, Minifier — to work with JSON effectively today and tomorrow.