Oh yes, this is not exclusive. As we like having many examples to understand a concept, we like to have things in many pieces, it helps us interact with it. In FP the set of ideas is so short and so abstract it ends up as an information ~vacuum. The other idioms let you assemble simpler less generic parts but at least it let's you acquire information, and that's something everybody likes.
Agreed: conceptual simplicity and therefore intelligibility at any given level of detail is a result of carefully designed and layered abstraction.
An important single-FP-language-codeball weakness is perhaps that of encouraging people to avoid clearly segregating these layers. Unix, by contrast, encourages a philosophy 'do one thing and do it well' for each smaller program, connecting them with simple interfaces, which arguably results in greater intelligibility.
You're not to come up with a simple design through any kind of coding techniques or any kind of programming language concepts. Simplicity has to be achieved above the code level before you get to the point which you worry about how you actually implement this thing in code. - Leslie Lamport
Law of Communications: The inevitable result of improved and enlarged communications between different levels in a hierarchy is a vastly increased area of misunderstanding.
