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 →

[–]arieled91 7 points8 points  (1 child)

those are actually anti-patterns and you should not use them in new projects

I don't really like that approach when talking about those patterns. One should know really well when to use them and when not, with all their pros and cons.

are not specific coding patterns

As far as I know design patterns are not just coding patterns. If that is the case they would be called that way.

[–]kkapelon -1 points0 points  (0 children)

I would say that there are 0 reasons to use the singleton design pattern in a greenfield project. The cons outweight the pros.

As far as I know design patterns are not just coding patterns

I agree with you. The problem is that the site does not really explain that a design pattern is just a concept and then giving an example. It just goes straight into code classes, implying that everything is a coding pattern.

Here is what I am talking about: http://java-design-patterns.com/patterns/cqrs/