title: Why are empty catch blocks a bad idea?
body: <p>I've just seen a <a href="https://stackoverflow.com/questions/1234278/good-ratio-of-catch-statements-to-lines-of-code">question on try-catch</a>, which people (including Jon Skeet) say empty catch blocks are a really bad idea? Why this? Is there no situation where an empty catch is not a wrong design decision?</p>
  
  <p>I mean, for instance, sometimes you want to get some additional info from somewhere (webservice, database) and you really don't care if you'll get this info or not. So you try to get it, and if anything happens, that's ok, I'll just add a "catch (Exception ignored) {}" and that's all</p>