Consequences of the Bridge Pattern
The Bridge pattern is intended to keep the interface to your client program constant while allowing you to change the actual kind of class you display or use. This can prevent you from recompiling a complicated set of user interface modules and only require that you recompile the bridge itself and the actual end display class.
You can extend the implementation class and the Bridge class separately, and usually without much interaction with each other.
You can hide implementation details from the client program much more easily.