Forget the Enterprise Architects, it's things like having to build a pipeline of 3 objects to just append a string to a file that gave Java its bad name.
That's the whole point. Pipelines are made up of interchangeable components. When a code base has to survive what it was supposed to do today to what it has to do 5, 10 or 15 years from now, you want those pipelines.
I disagree. For that I only need the possibility of replacing something simple with a pipeline, not necessity. The pipeline I am forced to build today may not only occur unnecessary - it runs the risk of having split the components along the wrong lines.
