But the logic that I have successfully used LINQ on: - operates on lists of objects, not database queries. - operates on small quantities of data. It doesn't

But the logic that I have successfully used LINQ on: - operates on lists of objects, not database queries. - operates on small quantities of data. It doesn't matter if there are only five items in a list. If you have to filter them, you have to filter them - is not that complex. We use foreaches as well, or a combination. LINQ is great for automating simple things, e.g. turn a loop to find an item into a .FirstOrDefault(x => x.SomeCondition). It would be interesting to see if, as our grasp of LINQ improves, we run into any of these supposed corner cases. But it hasn't happened yet.