Stephan van Hulst wrote:This reminds me of Haskell, where some programmers will try to impress each other by writing entire programs using types and type operations only. It invariably leads to an unreadable mess.
Jesse Silverman wrote:Just a comment about just how much popular sources distributing free programming/design advice differ in what they think a typical implementation of a particular design pattern might look in Java. The answer: way more than I was expecting.
Christopher Alexander wrote:Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice."
The Gang of Four wrote:The solution doesn't describe a particular concrete design or implementation, because a pattern is like a template that can be applied in many different situations. Instead, the pattern provides an abstract description of a design problem and how a general arrangement of elements (classes and objects in our case) solves it.
Jesse Silverman wrote:I realized the relative importance of some of them actually do vary from language to language.
Stephan van Hulst wrote:Java (as well as most other object oriented languages) employ single dispatch.
Junilu Lacar wrote:When I think of the Visitor pattern in Java, it's always double dispatch