Michel Feinstein

> Ok, understood, but memory footprint because of objects registered inside get_it should never be a problem Why? If we are registering Singletons, by definition those are long lived objects,...

Ok, drive safe, I live in Australia, so I going to bed soon.

> > Why? If we are registering Singletons, by definition those are long lived objects, we might have cache there that grows indefinitely. Anything that's long lived cannot be assured...

>Still you are doing premature optimization That's not premature optimization. Premature optimization is considered bad practice because we spend time and make our code more complex, trying to solve a...

> I said it before, LazySingletons won't save you from memory consumption in case that you expect that they will get instantiated at some time during app execution. They save...

I think the arguments about priority and time are valid, but they should not decide if a proposal is invalid. That is, in order for a proposal to be invalid,...

FYI I found this [injector](https://pub.dev/packages/injector) package and all it's singletons are lazily created, which I think supports my case that I am not the only one in the world who...

I know they are not related to you, but I think it's a good and obvious speculation, but I can ask them why they did it, if you want.

If I have a big app, with 100 Singletons, then if I don't use lazy Singleton factories, they will all be created as soon as the app starts. Many of...

> That is true, but IMHO you take 1000s of Dart objects to get into memory troubles. Images are always the problem, not simple objects. Yeah, but how do you...