What is the "whole idea" of a fluent interface if not specifically method chaining?
paulddraper has phrased it perfectly in answer to your previous post - chaining everything so that the process flow reads fluently from left to right. (I'm replying just to avoid leaving your question hanging.)
To suggest the pipeline proposal must not be referred to as a "fluent interface" would seem to me to be arguing semantics, ignoring the point behind the words, or the facts that they can have implied meanings or subtle changes over time.
I think the point behind the words is that it is a specific design pattern based on building DSLs using method chaining. I don't think pipelines, broadly, are an implementation of that design pattern. It's a way to string together function calls in a way that they read left-to-right, yes, but the spirit of "fluent interface" is not just "reads left-to-right." It's a specific pattern.
Re:jQuery 4.1.0
by everforward on Tuesday November 17, 2026 @08:26PM
(#50540702)
It can, but the typical usage I’m used to is far less structured and need not involve the value having the same type at every point. Eg something like
|> docker.listContainers() filter(x => x.name == “something”) first getNetwork getIpAddress toString ping
(ignore that some of these should be chained and some should be arguments, I haven’t read the proposal fully)
They’re doubly nice in Clojure because of the lazy evaluation. You can map a pipeline over a list and it will evaluate one at a time rather than pre-evaluating and allocating memory for the whole thing.
Maybe not precisely the same from a technical point of view but is it just pendantry to argue against someone referring to it as a fluent interface? Happy to learn and to be corrected if required.