Hold on it gets better (Angular Docs): "To solve the issue of lack of isolation, the directive declares a new isolated scope. An isolated scope does not protot

Hold on it gets better (Angular Docs): "To solve the issue of lack of isolation, the directive declares a new isolated scope. An isolated scope does not prototypically inherit from the child scope, and therefore we don't have to worry about accidentally clobbering any properties. However isolated scope creates a new problem: if a transcluded DOM is a child of the widget isolated scope then it will not be able to bind to anything. For this reason the transcluded scope is a child of the original scope, before the widget created an isolated scope for its local variables. This makes the transcluded and widget isolated scope siblings." Data-binding and re-usability should not be that hard.