Very Very well explained video. I am making an app and at first I too was going to be using it to store variables I needed globally, but turned out what I was looking for was AppStorage. But, now I need to make sure that only one instance of a class is made, and I appreciate that instead of just saying "Singletons are always bad" you explained the reasoning behind it. Thanks a ton!! :)
Hi thanks for the detailed video. i have a query like, if you said manage userdata or coredata functions with singletone then what will be the other approach to manage such kind of usage ? where we need to save or fetch same data multiple times .
Hi, You told about Singleton, But you didn’t explained what should be use instead of Singleton..? If I am not going to use singleton then what should I use. What patterns similar to Singleton.
As far as I understood, Singleton is good but the way it is being used is not correct, So there is no alternative of Singleton, it is good at its place. it shouldn't be misused. that's it.
As Pallav mentioned in his video if your application need only one instance of a class use singleton and if not than inject the required object as dependencies.
When i visit this video it has 996 views,82 likes & 10 comments in 2 days.. wish it will reach more people.. thanks for video & see ya in future 😃✌ 30.08.2022 08:39 pm ist
"Breaks SOLID"... man i'm sick of solid rules sometimes... we are in 2024 we can skip some of the solid rules... also Apple is using singleton in UserDefaults. Everyone uses userdefaults so this mean we break the solid shitprinciples?
Would love to have more videos on Design Pattern. Thanks for having such a quality content.
Very Very well explained video. I am making an app and at first I too was going to be using it to store variables I needed globally, but turned out what I was looking for was AppStorage. But, now I need to make sure that only one instance of a class is made, and I appreciate that instead of just saying "Singletons are always bad" you explained the reasoning behind it. Thanks a ton!! :)
Hi thanks for the detailed video. i have a query like, if you said manage userdata or coredata functions with singletone then what will be the other approach to manage such kind of usage ? where we need to save or fetch same data multiple times .
Hi, You told about Singleton, But you didn’t explained what should be use instead of Singleton..?
If I am not going to use singleton then what should I use. What patterns similar to Singleton.
As far as I understood, Singleton is good but the way it is being used is not correct, So there is no alternative of Singleton, it is good at its place. it shouldn't be misused.
that's it.
As Pallav mentioned in his video if your application need only one instance of a class use singleton and if not than inject the required object as dependencies.
yes if single instance is required go for it otherwise try to handle using injection using interface
Hi Pallav, great explanation about singleton. We are still waiting for the 6th video in the series of mastering concurrency.
Where you bought T-Shirts bro, Please refer
Hi, I like the way you explain.
Can you please create video on all architecture patterns and which to use when
Very useful, I was using as Global data store. I will change the way now.
Your all videos are top class
Thank you brother, such a nice content and well explained🤞🤞
Before understanding Dependency injection if we checkout this video then DI becomes more clear.....
Thank you for this.
When i visit this video it has 996 views,82 likes & 10 comments in 2 days.. wish it will reach more people.. thanks for video & see ya in future 😃✌
30.08.2022 08:39 pm ist
Love it
"Breaks SOLID"... man i'm sick of solid rules sometimes... we are in 2024 we can skip some of the solid rules... also Apple is using singleton in UserDefaults. Everyone uses userdefaults so this mean we break the solid shitprinciples?
Too fast