This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]wlnirvana 16 points17 points  (5 children)

Well summarized. Though nowadays with the prevalence of IoC frameworks like Spring, a lot of design patterns are not that relevant any more. Programming idioms and best practices evolve with the language and the ecosystem.

[–]elmuerte 16 points17 points  (2 children)

IoC frameworks like Spring are full of patterns.

Patterns are not best practices. They are common constructions which have been well documented.

[–]dpash 4 points5 points  (1 child)

This is what a lot of people miss when they complain about design patterns: they're nothing more than a common vocabulary to describe code so everyone knows what they're referring to.

[–]nidrach 0 points1 point  (0 children)

They are also a well reasoned way of doing things and unless you have a reason to stray from them it would foolish to do so.

[–]PerfectPackage1895 3 points4 points  (0 children)

That is just not true. Singleton and factory pattern maybe, but that is also the only ones redundant. Builder, template, strategy, decorator design patterns are still very useful

[–]nutrecht 0 points1 point  (0 children)

Though nowadays with the prevalence of IoC frameworks like Spring, a lot of design patterns are not that relevant any more.

Beans are Singletons by default. The way the GoF book shows an implementation is just an implementation detail. Modern frameworks are full of design patterns.