Given the popularity and ubiquitous use of the Singleton design pattern, how come that some developers continuously decry it as an “anti-pattern”? Can it really be that bad...?

In this session, we will first explain the rationale of why, yes, it can indeed be that bad. Then I'll provide a set of alternative approaches that you can use instead, with each of them avoid some or all of the issues that Singletons introduce into your code base.

Hopefully, this will allow everyone to just skip Singletons altogether and have valid tools at their disposal when they require shared instances or state.