proposal-pattern-matching VS ecma262

Compare proposal-pattern-matching vs ecma262 and see what are their differences.

ecma262

Status, process, and documents for ECMA-262 (by tc39)
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.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
proposal-pattern-matching ecma262
67 22
5,364 14,769
1.2% 0.5%
9.0 9.0
5 days ago 3 days ago
HTML HTML
MIT License GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

proposal-pattern-matching

Posts with mentions or reviews of proposal-pattern-matching. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-29.
  • Coming to grips with JS: a Rubyist's deep dive
    16 projects | dev.to | 29 Dec 2023
    Note, however, that there is a proposal to add pattern matching to JS.
  • Level up your Typescript game, functionally - Part 2
    2 projects | dev.to | 25 Nov 2023
    There's an ECMAScript proposal that is in the works to add this feature to the language! It's going to look something like this.
  • Building React Components Using Unions in TypeScript
    15 projects | dev.to | 1 Oct 2023
    More importantly, TypeScript typically commits to build things into itself when the proposal in JavaScript reaches Stage 3. The pattern matching proposal in JavaScript is Stage 1, but depends on many other proposals as well that may or may not need to be at Stage 3 as well for it to work. This particular proposal is interested on pattern matching on JavaScript Objects and other primitives, just like Python does with it’s native primitives. These are also dynamic types which helps in some areas, but makes it harder than others. Additionally, the JavaScript type annotations proposal needs to possibly account for this. So it’s going to be awhile. Like many years.
  • Explicit Software Design. Preliminary Conclusions
    3 projects | dev.to | 18 Sep 2023
    For true™ functional programming in JS, native pattern matching and partial function application are missing (at least for now: 1, 2). For proper OOP, it lacks real interfaces and compile-time dependency injection.
  • TypeScript Is Surprisingly OK for Compilers
    14 projects | news.ycombinator.com | 18 Aug 2023
    The proposal for pattern matching syntax seems more akin to what they're looking for.

    https://github.com/tc39/proposal-pattern-matching

  • [AskJS] C# in every Node.js job posting?
    2 projects | /r/javascript | 7 Jun 2023
    There's a proposal to add something like that to JavaScript but it's been stuck in limbo since 2017 although there are libraries like ts-pattern which implement it already.
  • [AskTS] What do you think will be the future of runtime type checking?
    10 projects | /r/typescript | 28 May 2023
    I'll admit, it is easy to assert that the TypeScript language should not be involved in the matters of packages but I also wonder if we're moving towards a point where interfaces will be as common as namespaces and whether or not it would be sensible for the language to incorporate such type assertions into the language formally, after all, it already compiles to various forms of JavaScript and there is a stage 1 proposal submitted to the TC39 committee to give JavaScript pattern matching. If adopted, wouldn't it make sense to allow TypeScript to compile a type into a type guard for the native JavaScript pattern matcher?
  • Updates from the 96th TC39 meeting
    5 projects | /r/javascript | 19 May 2023
  • Mostly adequate guide to FP (in JavaScript)
    5 projects | news.ycombinator.com | 21 Mar 2023
    Both are active tc39 proposals :)

    https://github.com/tc39/proposal-pipeline-operator - Stage 2

    https://github.com/tc39/proposal-pattern-matching - Stage 1

    Hopefully we get both in the next couple of years.

  • CoffeeScript for TypeScript
    5 projects | news.ycombinator.com | 27 Feb 2023
    We often add promising TC39 proposals into Civet so people can experiment without waiting.

    We've added https://github.com/tc39/proposal-pipeline-operator, a variant of https://github.com/tc39/proposal-pattern-matching, a variant of https://github.com/tc39/proposal-string-dedent and others.

    Since our goal is to be 99% compatible with ES we'll need to accommodate any proposals that become standard and pick up anything TC39 leaves on the table (rest parameters in any position, etc.)

ecma262

Posts with mentions or reviews of ecma262. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-19.
  • TC39: Add Object.groupBy and Map.groupBy
    6 projects | news.ycombinator.com | 19 Dec 2023
  • The "well-known" Symbols in JavaScript
    1 project | dev.to | 15 Dec 2023
    These aren't valid JavaScript (@@iterator would throw an error). They are actually internal Symbols used in JavaScript. They are used to implement features like iteration, instanceOf, and such internally. They actually might get removed or changed
  • 📦🔓Closures in JavaScript decoded
    1 project | dev.to | 19 Nov 2023
    Note that in previous editions, the ECMAScript® Language Specification used the term "lexical environment" before it decided to rename it to "Environment Record" so you might encounter this term in other definitions and tutorials.
  • Document.all Willful Violation
    1 project | news.ycombinator.com | 15 Oct 2023
  • ES2023 Candidate source code + specification
    1 project | /r/programming | 10 Apr 2023
  • ES2023 candidate source code + spec
    5 projects | /r/javascript | 10 Apr 2023
  • The Evolution of JavaScript
    1 project | dev.to | 22 Aug 2022
    For a new specification to be written, you need two things, a_ technical committee_, and a standard. The standard specification for JavaScript is called ECMA-262, and the technical committee is Technical Committee-39(TC39).
  • Why Async/Await Is More Than Just Syntactic Sugar
    3 projects | /r/javascript | 12 Aug 2022
  • Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
    11 projects | news.ycombinator.com | 12 Jul 2022
    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)
    6 projects | news.ycombinator.com | 15 Jun 2022
    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

What are some alternatives?

When comparing proposal-pattern-matching and ecma262 you can also consider the following projects:

fp-ts - Functional programming in TypeScript

spec - WebAssembly specification, reference interpreter, and test suite.

package.elm-lang.org - website for browsing packages and exploring documentation

proposal-ptc-syntax - Discussion and specification for an explicit syntactic opt-in for Tail Calls.

content - The content behind MDN Web Docs

TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.

io-ts - Runtime type system for IO decoding/encoding

proposal-record-tuple - ECMAScript proposal for the Record and Tuple value types. | Stage 2: it will change!

uwm-masters-thesis - My thesis for my Master's in Computer Science degree from the University of Wisconsin - Milwaukee.

ts-pattern - 🎨 The exhaustive Pattern Matching library for TypeScript, with smart type inference.

telegraf - Modern Telegram Bot Framework for Node.js