I looked at several explanations before watching this. Yours finally made it simple and easy to understand. Thank you.

Amazing video, would love to see more, though I suggest that you add a UML diagram in the future.

It's very simple explanation, but also it's so useful, thanks for explanation!

Quick and well explained, thanks!

Great video!! It may help that we reuse the variable "pizza" and keep re-assigning it to each decorator instance. It makes it clearer that "one thing" is being transformed through decorations. IPizza pizza = new Pizza(); pizza = new CheeseDecorator(pizza); pizza = new TomatoDecorator(pizza); pizza = new OnionDecorator(pizza); ....

Thanks for making this easier to understand!

This video gave the clear picture. Referring many sites didnt help me. Thanks a lot... Could you also provide videos on designing any architecture

Wow, really clarified it to me, thanks!

Man, you nailed it. If you can made me understand this, you're good at explanation! lol

Great Job. Thank you for this Charitable Endeavour.

Finally Eminem explained it very well. Thanks alot.

Thanks for this video!

thank you so much for this simple explanation.

nice and clean code, clear explanation. thanks.

That's pretty good. Thanks for the explanation.

Best explanation ! I've never had before Thanks so much

the video was very good, it dealt with in a simple way, I missed UnitTest and how to do the injection depedency could you include these steps in the next videos? example using FluentAssertion.

Thank you!

Great and very clean video, thank you!

This was an amazing example, Thank you so much man!!!!

Great thanks

It was really simple.. Thank you

Thanks

Good man.

The simplicity is great for comprehension, but one question I still have is how to handle other methods not explicitly extended by the decorator.

nice and simple :p

wow...what a nice pizza..!! I mean nice tutorial 😂. Keep it up ❤️

Can I also re use the variable "pizza" instead of creating new variables with differenet names and passing them? So that I can only have one instance of pizza being upgraded until It got passed through all decorators?

What if I want to bundle that functionality into an Attribute so it's as simple as applying an Attribute to a Method and getting the functionality added?

Instead of calling each decorator reference by specific name, like onion decorator, cheese decorator, etc call them all "toppings" and that way you can interchange the order without having to change the references in their constructors.

lol i got a bit confused for a moment when you started talking about pizza. i thought it was some programming term i had never heard of

Lit!

Damn it, now I am craving for pizza

Who puts the cheese on the bottom? :D

your first example spells decorator wrong

OOP is unnecessarily complicated. I haven't seen any real world implementation of most of these "patterns". Most devs either don't have time or expertise or even interest/enthusiasm to go around playing with objects. People just write code for work. OOP creates more problems than it promises to solve by creating more technical jargon. Composition > Inheritance. That's why JS wins.

❤️🍕🧑‍💻