title: Drawbacks to always using live() instead of bind() for unique dom elements?
body: <p>When writing jQuery binding events, I typically use the <code>bind(</code>) aliases (<code>click()</code>, <code>submit()</code>, etc). </p>
  
  <p>But, the more I use dynamically generated content, the more I find its ambiguous as to when <code>bind()</code> won't work, and end up debugging for a half hour until I try <code>live()</code> and it works. </p>
  
  <p>Within the parameters of ID-selectors (like '<code>#foo</code>', not <code>.classes</code> or elements <code>('input')</code>):</p>
  
  <p>Are there any drawbacks to just always using <code>live()</code> instead of <code>bind()</code> for these types of bindings, besides the lack of convenient aliases, since there can only be one DOM element tied to a particular ID?</p>
  
  <p>===========</p>
  
  <p>EDIT: I'm <strong>not</strong> asking what the difference between <code>bind()</code> and <code>live()</code> are; that's been covered. I'm asking what are the drawbacks of just using live() by default, since the temptation is to do so in instances where you can't mistakenly overselect (ie, when you're using a <code>#uniqueDomElement</code>), and avoid thinking about when <code>bind()</code> is not appropriate. </p>