The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Ecma262 Alternatives
Similar projects and alternatives to ecma262
-
proposal-ptc-syntax
Discussion and specification for an explicit syntactic opt-in for Tail Calls.
-
proposal-pattern-matching
Pattern matching syntax for ECMAScript
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
spec
WebAssembly specification, reference interpreter, and test suite. (by WebAssembly)
-
TypeScript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
-
uwm-masters-thesis
My thesis for my Master's in Computer Science degree from the University of Wisconsin - Milwaukee.
-
Backbone.js
Give your JS App some Backbone with Models, Views, Collections, and Events
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
proposal-cancellation
Proposal for a Cancellation API for ECMAScript
-
proposal-iterator-helpers
Methods for working with iterators in ECMAScript
-
proposal-array-grouping
Discontinued A proposal to make grouping of array items easier
-
-
-
core
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web. (by vuejs)
-
-
Elixir
Elixir is a dynamic, functional language for building scalable and maintainable applications
-
-
-
WebKit
Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
ecma262 reviews and mentions
- TC39: Add Object.groupBy and Map.groupBy
- ES2023 candidate source code + spec
-
Why Async/Await Is More Than Just Syntactic Sugar
thanks for the detailed answer. It's worth pointing out that there was also a change of the spec behind await a while ago.
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
4. Proposed something else [ https://github.com/tc39/proposal-ptc-syntax ]
While apple is against Syntactic tail calls, they’re mainly just opposed to versions of it that would remove/unrequire the tail-call optimisation they already do: https://github.com/tc39/ecma262/issues/535
For the version of it that is backwards compatible, they wouldn’t need to do anything other than recognise it as valid syntax. Their main concern is that it "could add confusion with very little benefit."
-
What happened to proper tail calls in JavaScript? (2021)
The spec for STC has a critique of PTC:
- performance
- developer tools
- Error.stack
- cross-realm tail calls
- developer intent
See: https://github.com/tc39/proposal-ptc-syntax#issues-with-ptc
Apple's 2016 response as to why they won't implement STC is here: https://github.com/tc39/ecma262/issues/535
- STC is part of the spec and will take too long to change.
- Now that they've implemented support for PTC, they don't want to regress web pages that rely on it.
- They don't want to discourage vendors from implementing PTC by agreeing to STC.
- They don't want to introduce confusion.
Some of these arguments about confusion and delays seem wrong hindsight, since on every point things would have been better if they'd just agreed to the compromise of STC.
- It would have been part of the spec years ago
- STC would have had a clear way for web pages to know when tail calls could be relied on (and PTC would have been optional)
- Other vendors didn't implement PTC in any case, despite no agreement on STC
- There's even more confusion as things are now
- Why You Don’t Really Need Semicolons In JavaScript (and TypeScript) Anymore
-
Why does JSON.stringify() re-order keys?
How is unrelated? It's the actual proposal for the change to the spec that was accepted. It even links to the diff.
-
[AskJS] TIL StackOverflow monkeypatches the String prototype across its various sites.
Funny thing is I once opened the console on a Stack Overflow page to try out a few things to solve a problem I was having. I ended up programming in a reliance on String.splitOnLast(), believing "Oh! Nice, I didn't realize this had gone through TC39."
-
Vue.js is Wikimedia Foundation's future JavaScript framework
> The point is that all code starts as simple text, and is parsed and compiled into some lower layer
Yup
> What actually does the compilation is irrelevant.
Nope. It is relevant. For the stuff you put between script tags there's at the very least https://github.com/tc39/ecma262 that you can look at and tell exactly what's going on with your code.
With Vue (and, yes, React and Svelte and Angular): who knows? It might very well evalueate strings at runtime for all we know.
> All of these JS frameworks (React+JSX, Vue+HTML, Angular, Svelte, etc) require template compilation into an actual JS render function before a browser ever runs it,
Yup. It's an additional, different step before it can even get to the browser. The problem with this step is that for most of this code there's not even a coherent specification of what it is, and how it's compiled.
> and Vue's documentation already describes exactly what you can run
It really doesn't. For example, here's the "documentation" on v-for:
Expects: Array | Object | number | string | Iterable
-
A note from our sponsor - WorkOS
workos.com | 28 Mar 2024
Stats
tc39/ecma262 is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of ecma262 is HTML.