Mr. Fowler has written a nice series on using pipelines instead of iteration for processing collections.
On a similar note, I recently came across this presentation on reactive programming in Java which also notes the benefits of composing operations as pipelines (though with a particular focus on processing sequences of observable events since this is reactive java after all). If you read through the deck to the last slide, you'll notice a humorous meme which represents more concisely Fowler's main point.
I'm so glad this exists.
Obviously, as shown in my Joinery project, I'm a big fan of this programming style. It provides a powerful mechanism for expressing the kinds of operations that are required when operating on large amounts of data while yielding a very high signal:noise ratio when reading the code.
On a similar note, I recently came across this presentation on reactive programming in Java which also notes the benefits of composing operations as pipelines (though with a particular focus on processing sequences of observable events since this is reactive java after all). If you read through the deck to the last slide, you'll notice a humorous meme which represents more concisely Fowler's main point.
I'm so glad this exists.
Obviously, as shown in my Joinery project, I'm a big fan of this programming style. It provides a powerful mechanism for expressing the kinds of operations that are required when operating on large amounts of data while yielding a very high signal:noise ratio when reading the code.
No comments:
Post a Comment