Pipelining might be my favorite programming language feature
herecomesthemoon.net
Pipelining might be my favorite programming language feature
1–10 of 360 posts
Re: Pipelining might be my favorite programming language feature
#2The tidyverse folks in R have been using that for a while: https://magrittr.tidyverse.org/reference/pipe.html
Re: Pipelining might be my favorite programming language feature
#3This is why I love Scala so much
Re: Pipelining might be my favorite programming language feature
#4If Python object methods returned `self` by default instead of `None` you could do this in Python too!
This is my biggest complaint about Python.
Re: Pipelining might be my favorite programming language feature
#5LINQ is easily one of C#'s best features.
Re: Pipelining might be my favorite programming language feature
#6While the author claims "semantics beat syntax every day of the week," the entire article focuses on syntax preferences rather than semantic differences.
Pipelining can become hard to debug when chains get very long. The author doesn't address how hard it can be to identify which step in a long chain caused an error.
They do make fun of Python, however. But don't say much about why they don't like it other than showing a low-res photo of a rock with a pipe routed around it.
Ambiguity about what constitutes "pipelining" is the real issue here. The definition keeps shifting throughout the article. Is it method chaining? Operator overloading? First-class functions? The author uses examples that function very differently.
Re: Pipelining might be my favorite programming language feature
#7That's also why I enjoy elixir a lot.
The |> operator is really cool.
Re: Pipelining might be my favorite programming language feature
#8I miss F#
Re: Pipelining might be my favorite programming language feature
#9If Python object methods returned `self` by default instead of `None` you could do this in Python too! This is my biggest complaint about Python.
Re: Pipelining might be my favorite programming language feature
#10While the author claims "semantics beat syntax every day of the week," the entire article focuses on syntax preferences rather than semantic differences. Pipelining can become hard to debug when chains get very long. The author doesn't address how hard it can be to identify which step in a long chain caused an error. They do make fun of Python, however. But don't say much about why they don't like it other than showi…
The article also clearly points that that it's just a hot-take, and to not take it too seriously.