Excessive use of Guava’s functional programming idioms can lead to
verbose, confusing, unreadable, and inefficient code. These are by far
the most easily (and most commonly) abused parts of Guava, and when
you go to preposterous lengths to make your code “a one-liner,” the
Guava team weeps.
Please be sure, when using Guava’s functional utilities, that the
traditional imperative way of doing things isn’t more readable. Try
writing it out. Was that so bad? Was that more readable than the
preposterously awkward functional approach you were about to try?
由于开销太高,所以对功能性成语的重视过多对Java 7来说不太了解(参见vertical problem).这将随Java 8而改变,这将改变Java库和程序在详细级别上的设计方式.在Java 7中,在Java中有意义的事情将在某种程度上在Java 8中被阻止.这将激发新版的Effective Java和许多新的API.