title: `perl -pe` vs `sed`, performance-wise
body: <p>On OSX, the system <code>sed</code> seems, at times, a bit limited regarding regular expressions and some escape characters — so much, that I end up using <code>perl -pe</code> a fair bit of the time, and now I’m wondering if I should care about using <code>sed</code> at all.</p>
  
  <p>I usually need this when piping a lot of commands in a row, usually calling <code>sed</code> and <code>perl</code> multiple times during its execution, and I’d like to know if I should use <code>sed</code> when it does the job, using <code>perl</code> only when it is necessary. I’m interested in this from a performance point of view (having multiple commands of this kind in a script can make a difference in the end), but if there are any other considerations you deem worthy of mentioning, they’re welcome, naturally.</p>