I know you've said this several times. And I'm being sincere when I say that I just don't "get" how LINQ to SQL feels like .NET has moved closer to VFP. (IMO, LINQ to SQL is the weak "link", no pun intended, of LINQ).

Perhaps the current scenario is a bit like a Cardiologist and an Orthopedist discussing the correct way to handle a bleeding vessel. The Orthopedist decides that the Cardiologist is a loser for closing arteries with peensy-weensy little sutures; if a vessel bleeds, just fry it with the diathermy. And if the Cardiologist observes that frying coronary vessels seems unlikely to benefit the patient, the Orthopedist hoots and hollers because you don't need to go via the chest to replace a knee joint.