The discussion was about how difficult was to map the db to an object model, how 'transparent' can persistence be, and the fact that noone wants to write ADO.NET code manually anymore.I think it is a fair question to ask why Microsoft is so late to the table with O/R mapping? Many problems and solutions have been addressed in academia and industry for well over five years.
Waiting for the one, true, API (which will certainly have faults... this is software) is stretching out another couple of years, apparently, at best.
Do you think I like picking on Microsoft? It's just the company has never seemed to grasp that software has to evolve, or maybe it's just that I've never grasped the business sense of their "rewrite the entire API just once" approach to Longhorn. I can only assume there is great business sense in this. Technically it can't hold up, and so will cost "us" money for years to come.