Re:A proposal for adding a pipe operator to JavaScript
by azangru on Tuesday October 19, 2021 @12:24PM
(#28919966)
Wouldn't no pipes be better than hack pipes?
Once a feature gets in, it will never get out. Whereas until it gets in, we can still hope for F# pipes :-)
Re:A proposal for adding a pipe operator to JavaScript
by joshum97 on Tuesday October 19, 2021 @12:46PM
(#28920245)
We've suffered under "bad parts" in JavaScript before, and the solution was not to use them, which works out fine for the most part. But I tend to agree, adding a functional language feature built in a way that conflicts with Ramda and nearly all existing FP libraries is no better than simply using R.pipe.
Re:A proposal for adding a pipe operator to JavaScript
by zarzavat on Tuesday October 19, 2021 @09:15PM
(#28925717)
I personally prefer F# pipes as it leaves the door open for partial application in the future, whereas Hack pipes closes that door because any partial application would be duplication.
However, I feel like all the people using Ramda should just make their own language if they don't like the direction JS is going in. This is a "too many cooks spoil the broth" situation.
> To emphasize, it is likely that an attempt to switch from Hack pipes back to F# pipes will result in TC39 never agreeing to any pipes at all. PFA syntax is similarly facing an uphill battle in TC39 (see HISTORY.md).
While I can respect differences in opinion, this feels heavy handed.