title: What are the benefits of CursorLoaders?
body: <p>I use <code>Cursors</code> extensively in my app, to load and occasionally write information from and to a database. I have seen that Honeycomb and the Compatibility Package have new <code>Loader</code> classes designed to help with loading data in a "good" way. </p>
  
  <p>Essentially, are these new classes (in particular <code>CursorLoader</code>) considerably better than previous methods of managing data? What is the benefit of a <code>CursorLoader</code> over managed <code>Cursors</code> for example?</p>
  
  <p>And I use a <code>ContentProvider</code> to deal with data, which obviously takes <code>Uris</code> but how does this mesh with the <code>initLoader()</code> method? Must I set up each of my <code>Fragments</code> to use Loaders individually? And how unique does the id need to be for each loader, is it over the scope of my app or just a fragment? Is there any simple way of simply passing a <code>Uri</code> to a CursorLoader to query my data?</p>
  
  <p>All I can see at the moment is that Loaders add an unnecessary extra step to getting my data into my app, so can someone explain them to me better?</p>