proposal-pattern-matching
ECMAScript 6 compatibility table
proposal-pattern-matching | ECMAScript 6 compatibility table | |
---|---|---|
67 | 33 | |
5,344 | 4,406 | |
0.9% | 0.1% | |
9.0 | 5.2 | |
9 days ago | 8 days ago | |
HTML | HTML | |
MIT License | GNU General Public License v3.0 or later |
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
-
Coming to grips with JS: a Rubyist's deep dive
Note, however, that there is a proposal to add pattern matching to JS.
-
Level up your Typescript game, functionally - Part 2
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
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
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
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?
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?
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
-
Mostly adequate guide to FP (in JavaScript)
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
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.)
ECMAScript 6 compatibility table
-
TypeScript Is Surprisingly OK for Compilers
http://kangax.github.io/compat-table/es6/
This page lists features from es6 (and newer versions linked at the top) along with compliance to the spec. First column is the current browser, second is babel+corejs polyfills.
Overall, babel gets about 70% of the way there.
- Яндекс Браузер не переводит видео про обучение украинских танкистов, хотя другие видео с канала МО Британии переводит нормально
-
Brett Slatkin: Why am I building a new functional programming language?
Case in point: Tail Call Optimization has been part of the JS spec since ES6, but remains completely unimplemented in all mainstream browsers/engines besides Safari[1]. For all but the most predictable inputs, you're pretty much forced to use loops where recursion would otherwise be preferable.
Additional case in point: async Iterables cannot be processed as a piped stream. You must use the for await construct, which is a shame considering the FP niceties that the Array type already provides for more traditional lists. Once again, you are forced to use an imperative construct unless you specifically want to defeat the purpose of using an Iterable in the first place by trying to convert it into an Array (... and potentially choking in the process, I might add!).
[1]: https://kangax.github.io/compat-table/es6/
- [AskJS] Is there a detailed comparison chart that shows what's supported in JavaScript ES5 versus ES6?
-
A single developer has been maintaining core.js with little recognition or support. Almost all modern single page apps use core.js. Millions of downloads and hardly any compensation
Eventually the browsers started racing to near-full ES6 compatibility. I remember following ES6 progress in realtime with articles and with compatibility tables http://kangax.github.io/compat-table/es6/ . But many people are acting like that either didn't happen, or like it was a one and done thing (despite the ESNext naming shift to avoid the focus on numbers). So we see people just hand-waving away the importance of polyfills like in this gem:
-
Tell HN: Firefox Is an awesome browser right now
> https://kangax.github.io/compat-table/es6/
Oh man this was a rough one both for FF and Chrome but Chrome did perform better slightly on cursory glance.
Thanks for providing these links, they're definitely a good rule of thumb benchmarks to test new browsers
-
My 1st website "Claw Man" written in javascript
Javascript / CSS language syntax: can see availability for Javascript here - https://kangax.github.io/compat-table/es6/
-
Is there any legitimate reasons for the javascript hate?
I say this as a JS user, but there is no singular JavaScript (realistically, it's not even JavaScript but instead ECMAScript). There is no one place to go that lays out all of what the language can or can't do the way PHP and Python do. The ECMAScript board makes recommendations, then the browsers and runtimes implement features of the recommendations. This site does a good job laying out which features are implemented for browsers and runtimes based on the flavor of the ECMAScript standard. This unique experience can be especially frustrating for someone learning JavaScript and coming from another language that does not have this problem.
- JS Polyfills - Part 1
-
[AskJS] Is there a JavaScript library that will test all ES features on your browser and tell you which it supports and which it doesn't?
https://kangax.github.io/compat-table/es6/ has a column for "current browser"
What are some alternatives?
fp-ts - Functional programming in TypeScript
es6-features - ECMAScript 6: Feature Overview & Comparison
package.elm-lang.org - website for browsing packages and exploring documentation
Babel (Formerly 6to5) - 🐠 Babel is a compiler for writing next generation JavaScript.
content - The content behind MDN Web Docs
Traceur compiler - Traceur is a JavaScript.next-to-JavaScript-of-today compiler
ecma262 - Status, process, and documents for ECMA-262
es6-cheatsheet - ES2015 [ES6] cheatsheet containing tips, tricks, best practices and code snippets
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
es6features - Overview of ECMAScript 6 features
proposal-record-tuple - ECMAScript proposal for the Record and Tuple value types. | Stage 2: it will change!
Lebab - Turn your ES5 code into readable ES6. Lebab does the opposite of what Babel does.