For a comprehensive deep-dive into the subject of Software Design Patterns, check out Software Design Patterns: Best Practices for Developers, crea...
For further actions, you may consider blocking this person and/or reporting abuse
Keep in mind that Singletons and Observers are considered anti-patterns!
I've never heard of Observer being an anti-pattern. If anything, it usually comes highly recommended in enterprise-level software as a way to reduce tight coupling between components.
I know that singleton is considered an anti-pattern, but on some smaller systems where dependency injection isn't available, it sure is useful.
I've heard of singletons as anti-patterns, but observer as anti-pattern is new to me. Would you mind elaborating?
Maybe he means Event Bus systems
You are right, I was thinking what I just write, and seems like I got it wrong. The observer I had in mind was the observer you can find in Magento for example (Magento 2 docs)
Event Bus is bad,
Observer pattern is not.
I dont get why Event Bus is bad.
I think it's more like "can be" anti-patterns.
Dependency Injection > Singleton
Use DI to inject factories and use these factories to create new objects.
Welcome to my code ... well after I read Clean Code and refactored a lot.
Singleton is good pattern for create NullObject.
Observer is good for make loggers.