Damn man. That's a unique teaching ability to explain every reason. Nice.

My left ear loved this

Very well constructed, step by step explanation. Thank you!

Incredibly clear man THANKS

Awesome.....Haven't seen this indepth singleton implementation, mostly people just do a first level of implementation without thinking of the multithreaded environment.

Hey man, your videos are super awesome. Thank you so much for the good work

Thanks for the video, it was really useful.

Thanks for clear explanation!

Super clear 👏 Thank you !

Thank you so much for making this video. Helped a lot!

Nicely explained. Thank you!

Your videos are so so so good!! Thank You!!

Thank you so much for a well coordinated video!! Kudos to you

The only thing I have to say is 'Perfectly Awesome..........'. Thank you!

Great explaining skills, I read many documentation but I completely understood from your video

That was giga clear. Tanks buddy

thank you so much ,very clear

Good channel. I started reading Head First Design Pattern, but I think I'm gonna drop it and just learn from you.

That was a great explanation

overwhelmed

Thank you!

Excellent

the best i've seen

Absolutely love the video although the last third of the video took 90% of my brainpower to keep up

You are amazing bro, you nailed it, I will definitely subscribe to such an amazing and valuable content channel, wish you growth and wealth :)

amazing!

sick explanation and video

Not sure why you don't have much more views for this video. I don't think anyone explained the multi thread issue in any of the singleton pattern video. Great job and thank you.

Cool video! It would be dope if you could also explain an alternative approach of making a singleton using enums please. Oh, and numbering the videos would be really beginner-friendly and much appreciated by the viewers!

Great video. But how to we actually use it now? Should there also be a setter to update the variables?

Good explanation , one question if some one calls clone method on the singleton instance , it will create another object right ? do we have to override clone method and return same instance , please explain ?

I just found out about this channel and subscribed to it. Great Job! Although I think your volatile explanation is a bit wrong. I think volatile tells the OS that this variable will always be written/read to/from the RAM instead of the CPU cache memory. So let's dive in the example where we don't have volatile: Thread A enters the synchronized block and checks if instance is null (still haven't started initialization), at the same time thread B checks if instance is null outside the synchronized block and sees the instance to be null. Therefore thread B also tries to enter the synchronized block but will have to wait for thread A. Thread A after a successful initialization will exit the synchronized block and eventually return. But thread B on the other hand, inside the synchronized block will again see the instance to be null (since the instance variable might only be stored in the cache of a different CPU core where thread A was operating, and where thread B can't see), and will initialize it again. This will not be happening if the "instance" variable is declared volatile: Thread A enters the synchronized block and checks if instance is null (still haven't started initialization), at the same time thread B checks if instance is null outside the synchronized block and sees the instance to be null. Therefore thread B also tries to enter the synchronized block but will have to wait for thread A. Thread A after a successful initialization (will write instance to RAM directly instead of the CPU cache) will exit the synchronized block and eventually return. Now thread B, when checking again if the instance is null inside the synchronized block, will see that it is already initialized (since it will read directly from RAM) and will return that value. Correct me if I am wrong

So with this pattern you can replace a single simple method that instanciate 10 different classes (implementing the same interface/abstract class) in a switch by 10 new creator classes to respect "Open to extension Close to modification" .... That's AMAZING ... What a great idea that's so much better now. LOL

good

Good channel. Helped me a lot. However I would request you to put even more detail to compete with other channels.

OMG wow man

please explain eager and lazy instantion

What is the use of "private String data" field here? If i call the getInstance() function with some data string, it will not update the data field of the instance. The first getInstance() call will set the data value and it will never change again. What am I missing?

i want a written notes of what ever he said can someone help me?

If the singleton needs to call a web service to fetch the singleton data such as access token, where do you place the logic to invoke the web service? Do you put it inside the singleton class or outside? Please clarify.

After instance was initialised, it doesn't matter anymore what String data we pass as parameter to getInstance, it will always return the instance with the data when the method was called the first time. It this really the correct way of doing that?

I think there is one mistake. An additional 'instance =' At the end it says instance = result = new Singleton(data);

6:24 I don't get how volatile fixes the problem. It only makes thread B reread the variable from memory when returning it but the variable could still not be fully initialized by thread A.

Good explanation, but the second if condition is redundant, isn't it?

>country can't have two presidents San Marino has entered the chat

Very nice job. But we can still break this by serialize the object and deserialize it to create a duplicate object. I guess you should have covered that particular scenario on how to overcome that.

There is so much stuff there. This feels like it should be solved by just making the whole thing a global atribute.

"most used pattern" - As far as I know, many programmers call it an anti-pattern...

Cool, but you should use enum for that.

kichui bujhlam na

That was giga clear. Tanks buddy

Thank you!