i have rewatched so many times to make sure i have comprehend whats in the 8 mins :). Seasonal devs might grasp quick. Crisp and highly informative videos! thanks.
Wonderful. Now I understood that Java's Cloneable interface is nothing but prototype design pattern. When I read about Cloneable from Effective Java book, I didn't realise that this is prototype design pattern. Thank you very much @Geekific. I have observed one difference. With Cloneable instead of calling super class's copy constructor, it invokes super.clone()
It is a superb content. It took me 4-5 time of rewatch but now my concepts are clear. Thanks man <3
honestly your explantions are amazing
Very well explained. Thanks.
nice explanation and video! but I have a question, isn't this violating the single responsability principle? now the object has the responsability it is originally intented to do, but it is also responsable of generating clones of itself?
Deep, precise, and clear explanation. Thank you
I find the code in this video extremely confusing. Im having problems relating the spoken information to the written information D:
Thanks u, you saved my life <3 <3 <3 <3
How we are setting value of Class attribute in registery the attribute of Car class is private and there is no setters u have shown???
I think JavaScript works somehow this way
شكرا
what does super(car) do. time : 5:47
how are fields immutable when there is no final keyword there ??
can we do prototyping for differnt type of objects , suppose one is 'Fruit ', other is 'FruitDTO'
perfect
I didn't know that object of the same class can access the private fields of another object of the same class
Weird thing is that we trying to solve copying now... when arrays have Copy function, that just utilizes copy of data (memcopy) in RAM.
@anime4u568