title: Why jQuery 1.9+ attr() method not deprecated?
body: <p>Can I, a jQuery1.9+  software developer, "deprecate" the use of the <code>attr()</code> method in my day-by-day work?</p>
  
  <hr>
  
  <p>As showed in many questions,</p>
  
  <ul>
  <li><a href="https://stackoverflow.com/questions/5874652/prop-vs-attr">.prop() vs .attr()</a>  (main)</li>
  <li><a href="https://stackoverflow.com/q/15057281">jQuery attr vs. prop, there are a list of props?</a></li>
  <li><a href="https://stackoverflow.com/q/13247058">jQuery attr vs prop?</a></li>
  <li><a href="https://stackoverflow.com/q/14602773">Migrating jQuery 1.8.3 to 1.9.0 - Replacing deprecated .attr()</a></li>
  <li>... etc. ...</li>
  </ul>
  
  <p>there are a lot of confusion about <em>"use attr or use prop?"</em>, and, by my (developer's) view point, for all uses of <code>attr()</code> method, we can use <code>prop</code> instead:</p>
  
  <ol>
  <li><em>backward-compatibility</em>: coding new software not need this; </li>
  <li><em>performance</em>: <a href="http://ejohn.org/blog/jquery-16-and-attr/" rel="noreferrer">John says</a> "Accessing properties through the .attr() method will be slightly slower than accessing them directly through .prop()"; </li>
  <li><em>Change attribute value</em>: all can be changed by the <code>prop(name,newvalue)</code> method.</li>
  <li><em>Remove attribute</em>: all can be removed by the <code>removeProp(name)</code> method.</li>
  <li><em>Check HTML attribute values</em>: browser use DOM, all HTML was converted to DOM, and, if DOM affected the <code>attr(name)</code> method also affected. About "strong type" of prop: it is better than "html string value" (ex. "checked" vs <em>true</em>).</li>
  <li><em>Check if an attribute was defined</em> in the "HTML original code" (supposing that method  <code>attr</code> in your browser returns <em>undefined</em> if it is not)... Well, we need this in some piece of software?  <a href="http://jquery.com/upgrade-guide/1.9/#attr-versus-prop-" rel="noreferrer">At forms</a>, ".val() method is the recommended jQuery way to get or set the values of form"</li>
  <li><em>Cross-browser consistency</em>: both (not only attr) are consistent methods. (it is??).</li>
  </ol>
  
  <p>So, at this time (2013), I not see a good reason to use  <code>attr</code> method when developing new jQuery code... But, well, this is, in other words, the question: <strong>There are a good reason to use  <code>attr</code> method in my day-by-day tasks?</strong></p>