Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's only less noisy because of the simplistic nature of the example. In real world code, `one`, `two` and `three` and probably a chunk of code put together in a single line and it's difficult to find out what the hell they are doing. Concat together a few of these and that's a recipe for disaster. Less experienced engineers would add a comment at the top of the pipe chain explaining what's going on. More experienced engineers would divide and conquer and use temporary named variables (render commets useless).


Agreed. I'm not the one coming up with the one/two/three, I took it from the proposition.

Explanatory variables help understand the steps of the process, this |> operator is receipe for unmaintainable, expedited code.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: