7 ms·
In response to people repeatedly advocating for F# + partial application over Hack, TC39 responds with what is essentially a threat: > To emphasize, it is like
by joshum97 5y ago
In response to people repeatedly advocating for F# + partial application over Hack, TC39 responds with what is essentially a threat:
> 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.
- zarzavat 5y agoI 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.
- azangru 5y agoWouldn'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 :-)
- joshum97 5y agoWe'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.