m.invoke() vs. m()

[Ricky Clarkson]

"As mostly a language user (*) I don't care about implementation
complexity, compiler writers are born to suffer :-) as long as the
end-user's features/complexity tradeoff (if any) is ok."

The problems occur when the complexity is not entirely contained
within the compiler/IDE implementation.  If you can't follow which
method/closure will be called, you are likely to write more bugs than
otherwise.  If you can't follow it, chances are at least one compiler
or IDE will get it wrong for some period of time too.

In case of determined misreaders, this is a general point, and does
not serve to support or disagree with points made elsewhere in this
thread.

-- 
Ricky Clarkson
Java and Scala Programmer, AD Holdings
+44 1565 770804
Skype: ricky_clarkson
Google Talk: ricky.clarkson at gmail.com
Google Wave: ricky.clarkson at googlewave.com