title: Would it make sense to use directive instead of filter to speed up performance?
body: <p>It seems like angularjs 1.x filter is not recommended, with the reason given below:</p>
  
  <p><a href="http://blog.scalyr.com/2013/10/angularjs-1200ms-to-35ms/" rel="nofollow">http://blog.scalyr.com/2013/10/angularjs-1200ms-to-35ms/</a></p>
  
  <p>Angular runs every single filter twice per $digest cycle once something has changed. This is some pretty heavy lifting. The first run is from the $$watchers detecting any changes, the second run is to see if there are further changes that need updated values.</p>
  
  <hr>
  
  <p>I wonder if it make sense to either:</p>
  
  <ol>
  <li>Use bind-once with filter</li>
  <li>Write custom directive that ensures no additional watch is required?</li>
  </ol>