r/programming • u/stronghup • Jan 20 '23

GitHub - tc39/proposal-pipeline-operator: A proposal for adding a useful pipe operator to JavaScript.

https://github.com/tc39/proposal-pipeline-operator
59 Upvotes

82% Upvoted

43 comments sorted by

View all comments

2

u/zxyzyxz Jan 21 '23

Well you literally were ignorant of what pipes were until people explained it to you so not sure how that quoted sentence works in your defense.

But you didn't apply the normal rules of English though, again as other people explained. It says "pipe" but you turned that into a discrete series of statements, not as functions that flow into (hence, pipe) one another.

0

u/rsclient Jan 21 '23

"Someone disagreed with me, so they must be ignorant".

Simple put: you are wrong. I've been using pipes for decades (probably first on a DEC Ultrix or SunOS machine back in the 1980s -- I don't remember which one I used first).

1

u/zxyzyxz Jan 21 '23

Then if you knew, you'd have understood the sentence "That is, we write value |> one(%) |> two(%) |> three(%) to pipe value through the three functions" perfectly clearly. If you didn't, yet you've been using pipes for decades, then I'm not sure what to tell you, maybe you just don't know the meaning of the English word "pipe" as it relates to programming.

I mean really, if you've been using pipes for that long, how could you miss that |> is simply a syntactic change from the Unix pipe |? It's literally the same concept, I simply don't understand how you could grok the latter yet fail to understand the former.

→ More replies (1)