I can see where you're coming from, but I disagree about it not being
broken. One of the most important parts of development is naming. For
a flagrant extreme example, if Double was called Float, would it be
broken? Would people jump up and down about the broken-ness of the
JVM? But it
Stephen Kestle wrote:
The Closure in commons collections is not named well
[snip valid points]
So, what to do?
I would propose an interface called Processor. It is more intuitive and
has many real world examples that can anchor the term so that it makes
sense to the average (and functional!)
The Closure in commons collections is not named well: for
non-functional programmers it will induce a what's that?, and for
functional programmers it will confuse expectations.
From http://en.wikipedia.org/wiki/Closure_(computer_science):
A closure combines the code of a function with a