Show HN: A JavaScript function that looks and behaves like a pipe operator

Re:Show HN: A JavaScript function that looks and behaves lik... by knubie on Wednesday September 27, 2023 @06:20AM (#37672680)

I think the implication is that it's difficult to read because it's read non-linearly. You first need to start in the middle at `greeting`, then work your way out to `capitalize` on the left, then to `+ "!"` on the right, then work your way out one more layer to the left with `send`.

Some kind of pipe operator can make this easier to read by arranging the operations linearly from left to right (or top to bottom as is the case with this library). Although in my opinion this library has its own readability issues.

[ Parent | on HN ]

Re:Show HN: A JavaScript function that looks and behaves lik... by moritzwarhier on Wednesday September 27, 2023 @12:36PM (#37677273)

I agree. In the example case, I don't see why left-to-right or top-to-bottom would be more readable.

Sure, it is good most of the time, but operator precedence rules exist for a reason.

I don't want to read

  2.chain(x => x * 2).chain(f)

instead of

  f(2*x)

These patterns have their place for async programming, pure FP, streams and more.

They can also be a distraction.

E.g. the library introduces its own promise-unwrapping semantics and more.

I don't see the use for such a generic implementation, although I applaud the effort.

[ Parent | on HN ]