title: Angular: Rules on when to make something a custom pipe vs component
body: <p>Any rules on when to use a custom <strong>pipe</strong> and when to use a custom <strong>component</strong>?</p>
  
  <p>Could those be the rules of thumb (below) ?</p>
  
  <ul>
  <li>use a component if non-plaintext html is required? Inspired by: <a href="https://stackoverflow.com/a/34504446/170451">https://stackoverflow.com/a/34504446/170451</a></li>
  <li>use pipe if something is not interactive (static output)?</li>
  </ul>
  
  <p>Documentation does not seem to answer this question directly: <a href="https://angular.io/docs/ts/latest/guide/pipes.html" rel="nofollow noreferrer">https://angular.io/docs/ts/latest/guide/pipes.html</a></p>
  
  <p>Could pipes be considered «poor man's components?»</p>
  
  <hr>
  
  <p>Are there some advantages of <strong>pipes</strong> over <strong>components</strong>?</p>
  
  <p>My guesses:</p>
  
  <ul>
  <li>shorter syntaxes / expressiveness</li>
  <li>performance benefits (build-time? run-time?)</li>
  <li>benefits when working with plain-text?</li>
  </ul>
  
  <hr>
  
  <p>Does this statement (which is a guess written by me) hold true?</p>
  
  <pre><code>Everything that can be done with a pipe,
  can be done (though perhaps at a higher cost) with a component as well?
  </code></pre>