> It's not about line breaks, it's about the order of applying the operations For me, it's both. Honestly, I find it much less readable the way you're split it

> It's not about line breaks, it's about the order of applying the operations For me, it's both. Honestly, I find it much less readable the way you're split it up. The way I had it makes it very easy for me to read it in reverse; map, filter, map, collect > Also see how this still reads fine despite being one line It doesn't read fine, to me. I have to spend mental effort figuring out what the various "steps" are. Effort that I don't need to spend when they're split across lines. For me, it's a "forest for the trees" kind of thing. I like being able to look at the code casually and see what it's doing at a high level. Then, if I want to see the details, I can look more closely at the code.