Excellent question! While filming, this question struck me as well. It's really quite hairy. They are deviously similar and I keep forgetting the nuances :) TLDR; I agree with you. But, let's define the concepts... 1) The adapter adapter pattern changes the interface but does not change the implementation. 2) The proxy pattern changes the implementation but does not change the interface. 3) The decorator pattern changes the implementation but does not change the interface. 4) The facade pattern is a high-level level abstraction over low-level components, where the interface is changed. So, I guess it boils down to proxy vs decorator. The deprecation example I gave could, depending on the scenario, probably be technically considered decorator pattern. But then again, it's a too simplistic example that doesn't really take advantage of the true power of decorator pattern. So I agree with your comment. Further, my example becomes even more silly if we look at it in a statically typed language (I usually work in dynamically typed languages and was thinking of that when I blurted out the example). In the decorator pattern we have the two interfaces Component and Decorator. The old class we want to deprecate is a Component, but if we were to use Decorator Pattern to deprecate it then the new concrete class would have to be a Decorator which in turn is a Component. From an abstraction point of view, this is actually a good thing because the abstract Decorator could then make sure to delegate all method calls to the decorated Component, which leaves the concrete Decorator with the job of only implementing the few methods it wants to change. But then again... this is probably massive overkill, and you'd be better off just throwing in a proxy where the proxied object is dependency injected into the proxy. Interesting excursion :) Thank you for the comment. I need to think my examples through a bit better before rocking it :) Ps. I've got an older video on Adapter vs Facade vs Proxy here: ukposts.info/have/v-deo/oIR0Z6ikiXh62ac.html

Thank you for a very detailed and educational answer :) I still haven't touched the Proxy pattern which I'll do next and that is probably the reason why Adapter and Facade were the first that came to mind. For now it makes sense why and how to use the Decorator for deprecation even if it is an overkill. It's good to have these examples in your videos because they give us the opportunity to think about them and ask when unclear, so keep it up, it's all good :) I enjoy the Code Walks as well, especially liked the one about VR/AR and moving coding away from the monitor+keyboard environment!

Christopher Okhravi, Thank you very much for these amazing videos.

In this case , i think proxy pattern makes sense. Awesome video Chris .

BEST saxo ever

This is true. I have never been patient enough to watch a vid for a whole hour and still wanting to watch the next one

@@sshanzel i concur

Same for me!

noob

One of the best comments on UKposts :) :) ;)

execuse me this is the best not one of the best. believe me i went trought them all.

@@ChristopherOkhravi (One of the best comm......) 😁 yes, it is true.

Not one of the best. But actually THE BEST OF EM ALL

Thank you for the kind words. And thanks for watching.

That's awesome! I'm glad to hear the videos complement the contents of the book. Thank you very much for sharing and for watching :)

Osama Tamimi Thanks for taking the time to write this comment. I appreciate it. I'm glad the video is useful :)

Thank you for the kind words :) :)