3 ms·

Hard disagree. Singleton is a tool, and like any tool it has trade-offs. Singletons help you target a very specific, useful time in your application: after it's

Hard disagree. Singleton is a tool, and like any tool it has trade-offs. Singletons help you target a very specific, useful time in your application: after it's compiled, but before it's serving requests. You can call this the "initialization time". Within this time, singletons help you organize the one-off components of your application - canonincally, things like connection/thread pools. But hey, thanks for the hot take.

cr__ 5y ago
Why not explicitly initialize the one-off components and pass them to the other parts of the system that need them as arguments so the system is testable and dependencies are clear? (I know why, generally—low-expressivity languages make it nightmarish to actually do this.)
nedbat 5y ago
If you need just one, make just one. Why should the class enforce it?
- thfuran 5y ago
  Why deliberately avoid enforcing design constraints? I mean, why not just make everything a void * and cast as needed and promise not to mess up?
  - nedbat 5y ago
    You can enforce the constraint, but it shouldn't be in the class itself. How to you make instances for tests?