Conversation
This appears to be going backwards in terms of acceptance. For example: https://bugzilla.mozilla.org/show_bug.cgi?id=1708546 We're headed toward dropping it from BCD. See: mdn/browser-compat-data#6957 (comment)
To clarify, the pipe-operator is no longer going backwards, but it has been in flux (there are at least three competing syntax proposals, as summarized by @tabatkins), and it had indeed stagnated between 2019 and 2020 due to that syntax deadlock and also to flagging browser-vendor interest. However, after the State of JS survey of 2020 published last January that its fourth top answer to “What do you feel is currently missing from JavaScript?” was the pipe operator, and after @tabatkins published his essay, then TC39’s interest in the proposal revived. @littledan presented about it again in March, after which its TC39 champion switched to @tabatkins. I do think it is a good idea to remove documentation about the pipe operator from MDN until its proposal(s) advances further and its syntax settles more. It is certainly still in great flux. But its future at least now looks somewhat brighter than it had been in 2020. |
|
@js-choi Nice to see that work on the proposal continues. Thank you for this update! |
3 participants
The pipeline operator (
|>) appears to be going backwards in terms of acceptance. This PR redirects the page to the parent operators page, then removes the content.https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Pipeline_operator
Firefox removed the prototype: https://bugzilla.mozilla.org/show_bug.cgi?id=1708546
BCD is removing the all-
falsedata for this feature: mdn/browser-compat-data#6957 (comment)Now that we're in git, I imagine it will be easy to recover this should the proposal be revived.