title: Polymer and globals
body: <p>I'm getting into Polymer and i like the deps resolution approach using imports.<br>
  And i like the extending capability through the <code>behaviors</code> config.<br>
  However, there's something that doesn't feel comfortable to me, about behaviors in particular.<br>
  Looking at the <a href="https://github.com/PolymerElements" rel="nofollow">PolymerElements</a> code i see that behaviors, are defined inside their own html in the global object <code>Polymer</code> and then referenced directly when imported by another component..<br>
  For example:</p>
  
  <p><code>paper-button</code> imports <code>paper-button-behavior</code>
  <a href="https://github.com/PolymerElements/paper-button/blob/master/paper-button.html#L14" rel="nofollow">https://github.com/PolymerElements/paper-button/blob/master/paper-button.html#L14</a></p>
  
  <p>it then defines <code>paper-button-behavior</code> as behavior referencing from global <code>Polymer.PaperButtonBehavior</code>
  <a href="https://github.com/PolymerElements/paper-button/blob/master/paper-button.html#L144" rel="nofollow">https://github.com/PolymerElements/paper-button/blob/master/paper-button.html#L144</a></p>
  
  <p>wich is defined here (the imported html)
  <a href="https://github.com/PolymerElements/paper-behaviors/blob/master/paper-button-behavior.html#L49" rel="nofollow">https://github.com/PolymerElements/paper-behaviors/blob/master/paper-button-behavior.html#L49</a></p>
  
  <p>Ain't it an anti-pattern, especially as typically an app will not use Polymer's world exclusively?</p>