Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade past ECMAScript 5.1 #56

Open
dfabulich opened this issue Apr 18, 2024 · 0 comments
Open

Upgrade past ECMAScript 5.1 #56

dfabulich opened this issue Apr 18, 2024 · 0 comments
Assignees

Comments

@dfabulich
Copy link

JSON5 is defined as "JSON for Humans," but it arbitrarily limits itself to the features available in ECMAScript 5.1.

(Except for unescaped line and paragraph separator characters. So, technically, JSON5 is compatible with ES2019.)

But there have been two other additions to JavaScript's literal syntax that would be applicable to JSON5, in between ECMAScript 5.1 and ES2019:

Since ES2019, there's also:

In #23 I see that @jordanbtucker wrote this by way of explanation:

We aim to keep JSON5 simple by only adding features from ES5. This keeps JSON5 easy to implement and prevents scope creep.

The TC-39 committee is already committed to minimizing scope creep for JavaScript. In fifteen years, there have only been five new literals introduced, all listed above.

Supporting all of the literals that the current latest version of JavaScript supports isn't "scope creep." It's committing to JSON5's true definition, "JSON for Humans."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants