News for hackers. Stuff that matters.
Re:Singleton Is a Bad Idea by mikece on Sunday April 10, 2022 @11:44AM (#30978114)
> These ways are simpler than the usual gymnastics to implement singletons.

Is this a python-centric complaint? I usually write C# and Singletons are just one of a few different scope types for defining objects in the IoC container, no easier, harder, rarer or more common than any other class type.

Re:Singleton Is a Bad Idea by emodendroket on Sunday April 10, 2022 @01:59PM (#30979753)
I would consider creating a dependency as a singleton in your composition root different from a "true" singleton, because the latter involves baking the assumption that it will be a singleton into all callers rather than injecting it.
Re:Singleton Is a Bad Idea by Matthias247 on Sunday April 10, 2022 @02:02PM (#30979790)
I guess so. My favorite problem with singletons is testability. How can you properly mock/observe/etc it inside a test case, if lots of test-cases are executed in parallel. With a real global object it can be tricky. But if the object is not global because an IOC container might still create a fresh one per test, it wouldn't be an issue.
Re:Singleton Is a Bad Idea by moron4hire on Sunday April 10, 2022 @02:49PM (#30980383)
The Singleton of .NET IoC containers is not the same thing as the Singleton pattern. It's called a Singleton because the DI controller will make sure only one instance is available. But the Singleton pattern has the class itself making sure it can have only one instance. The mixing of concerns is the problem with the Singleton pattern. With a DI controller, you can change the lifetime of the instance without having to change the class definition itself. With the Singleton pattern, changing the instance lifetime requires changing every utilization site.
Re:Singleton Is a Bad Idea by brtkdotse on Sunday April 10, 2022 @02:41PM (#30980278)
Came here to write this. In .NET it’s easier to just follow the normal DI pattern and inject your desired singleton with AddSingleton<>