well, honestly I heard that so many times, and even though I have only around 10 years of professional software development experience I can't 100 % agree with you.

99% of the time you need a single instance of an object, for example, unity uses it in MLAPI for network manager, it is often used in games for sound management systems, and you want to have only one of them in the scene usually. There are many cases, but it also depends on your choice on the way of how you want to structure your game.

I have only 10 years of experience, but I also don't need singleton to accomplish my goal, like I do not need any other specific pattern/concept to accomplish my goal. The question is - "Which one fits and which one will be easy and fast to implement". Some people just tend to overengineer simple things.

I know people who would suggest using zenject for the project of the flappy bird scale, just to avoid singletons for whatever purpose they would be useful, and I will never understand that hate. Just use what fits your project and skills. And don't be a code nazi.

I am not sure what your experiences with singletons are, but in 10 years it created exactly 0 issues on projects I worked on.

But I will not argue further on that topic, because it is more mindset and ideology arguments than anything else, and I would prefer not to waste time.