From 3ac3385f70b3e86a3256144749f72ad4b4aa9118 Mon Sep 17 00:00:00 2001 From: Evan Hemsley Date: Tue, 21 Jul 2020 15:33:59 -0700 Subject: [PATCH] take out insert video here --- content/pong/opponent/_index.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/content/pong/opponent/_index.md b/content/pong/opponent/_index.md index 49131a2..a751f78 100644 --- a/content/pong/opponent/_index.md +++ b/content/pong/opponent/_index.md @@ -192,12 +192,6 @@ Finally, let's send a message to spawn the computer-controlled paddle. ``` -*Insert video here* - - - If we were doing this in an object-oriented way, we would have had to inherit from the paddle or introduce another state to the paddle, thus forcing us to refactor or increase the complexity of the paddle object itself. Notice how in our case we didn't really have to change any of our existing logic - all we had to do was create new components and write a new engine for producing behavior from those components, while getting to retain all the behavior we got from the other paddle components. See how clean and de-coupled this is? This is the power of _composition_ over _inheritance_.