Do one thing, and do it extremely well is a simplified version of the Unix design philosophy. And this can be applied various levels of abstraction, including within OO programs.
I fail to see the controversy in this.
I'm pretty sure it's an analogy.
> It is about interfaces, streams and common intermediate data representation
And this is what modularity is all about too.
> There is nothing from UNIX Philosophy there, just a modularity
Read the second paragraph: http://www.linfo.org/unix_philosophy.html
In the same way, Lisp without an underlying list structure is just a prefix notation.
It's true that Unix isn't object-oriented, but the principles that made it great are ones that object-oriented developers can benefit from studying. And given the long lifetime and wide use of the Unix model, it's a great object of study.
Of course because these principles are basic programming principles. Yet , this has nothing to do directly with object orientation. There is no "object orientation" in the way unix works.
Who said there was?
On the other hand, I think the article didn't do the topic justice because it only really talked about separation of concerns. It never really talked about the "pipes". And, as you mention, the consistency of "communication via text" is what makes those pieces so able to be composed.
And, in software, some of the "pipes" we've come up with have often been truly dreadful (COM, anyone?).
Scheme or Erlang are real examples of following similar philosophy.
Modularity is much more basic concept, underlying any software. It is about spiting code into blocks for later reuse, named, in case of procedures, or anonymous in case of blocks or lambdas.
The notion that smaller, share-nothing procedures doing only one well-defined task are better than bloated and close-coupled ones is a general one.
So, do not try to mislead others. There is nothing from UNIX Philosophy there, just a basic concept of modularity.