\n\nOne of the things that we do by defining design patterns is we create a common language that we can use to explain and express ourselves. When I say to you \u00e2\u0080\u009cI used an Adapter\u00e2\u0080\u009d or \u00e2\u0080\u009cI implemented the Factory pattern\u00e2\u0080\u009d, that should conjure up a specific image in your mind of object relationships and behaviors, even if you don\u00e2\u0080\u0099t know my specific use case or problem domain.
\nWhen we use these terms incorrectly, we not only devalue them, we confuse developers. For one of the most up-and-coming frameworks to use a technical term so incorrectly is disturbing. It breaks down the vocabulary that technical people use to communicate with each other, because there are now two very different definitions floating around with the same name.
\nOf course, Laravel\u00e2\u0080\u0099s Facades are in fact well-designed proxies implementing the Proxy Pattern. There\u00e2\u0080\u0099s nothing wrong with that: as a developer, it\u00e2\u0080\u0099s up to you to decide how and what patterns you\u00e2\u0080\u0099re willing to accept in your framework, and to write your application however you wish. All I ask is that we stop calling them Facades.
\n
Hear hear. Via Let\u00e2\u0080\u0099s Talk About Facades | BrandonSavage.net.
\n" }