title: LLBLGEN Pro and EF4 ORMs comparison
body: <p>New year - new startup :)
  We are chosing ORM. I personally worked with LLBLGEN last years.
  I've looked through EF4 today and have found that its functionality is close to llblgen.
  (filtering, sorting, grouping, working with stored procedures and functions, working with graphs of objects (prefetch path), lazyLoad).</p>
  
  <p>I know that llblgen doesn't support POCO, that means that it is required to write additional (or more complex) code to decouple it from Domain.</p>
  
  <p>I don't think that llblgen license is con as llblgen is real successful alternative to Microsoft's orms and it is cool that we have such alternatives.</p>
  
  <p>I didn't find any concrete comparison of these orms in stackoverflow. 
  Just something like "If it is not critical to pay maney then use llblgen" :).</p>
  
  <p>So I just want to list pros and cons of LLBLGEN and EF4. (ORMs functionality only without designers features)</p>