Of course, Ruby is a bit of a mixed bag, but for the applications where it fits, it can be very nice.
@source >>> map { ... } >>> grep { ... } >>> my @sink;
Plus of course there's many languages with a |> operator so you can do
g(x) |> f
I'm not convinced that left-to-right is -always- the best option and prefer having the choice of both, but I wouldn't be at all surprised if a survey of developers found that if they could only pick one they'd pick left-to-right, and while I'd find it hard to choose for myself alone I'd probably pick left-to-right on the basis that it'd likely make it easier to onboard people to any given codebase.
my @sink = @source.map({...}).grep({...}).sort;
my @sink = @source.hyper.map({...}).grep({...}).sort.list;
my @sink;
@source ==> map {...} ==> grep {...} ==> sort ==> @sink;
Yes, yes it was.
Clarifications and elaborations much appreciated.
That's why I use and msybe tend to abuse the `->` and `->>` macros in Clojure and the pipe operator `|>` in Elixir.
Hopefully soon in JS as well, if I've read correctly.
That's one thing I will say after coming from Perl/PHP to Java, is that despite its verbosity and the uselessness of having to write .stream(), I much prefer Java's stream.map(...).filter(...) syntax over the more functional-style filter(map(list, ..), ..) syntax. The Java syntax reads left-to-right, which is the order you want when you're thinking about code, and also as you say writing it. I think if I were creating a programming language I too would try to make stuff read left-to-right as much as possible.