>Somthing similar here back in October:
>
>Wednesday, October 29, 2008 5:36 PM by dpblogs
>Update on LINQ to SQL and LINQ to Entities Roadmap
>Since the release of LINQ to SQL and the Entity Framework, many questions have been raised about the future plans for the technologies and how they will relate to each other long term.
>During this week of PDC we are now at a point, with the announcement of Visual Studio 10 and the .NET Framework 4.0, that we can provide more clarity on our direction.
>
>We have seen great momentum with LINQ in the last year. In .NET Framework 3.5 we released several LINQ providers, including LINQ to SQL which set the bar for a great programming model with LINQ over relational databases. In .NET 3.5 SP1, we followed up that investment with the Entity Framework enabling developers to build more advanced scenarios and to use LINQ against any database including SQL Server, Oracle, DB2, MySQL, etc.
>
>We’re making significant investments in the Entity Framework such that as of .NET 4.0 the Entity Framework will be our recommended data access solution for LINQ to relational scenarios. We are listening to customers regarding LINQ to SQL and will continue to evolve the product based on feedback we receive from the community as well.
>
>Tim Mallalieu
>Program Manager, LINQ to SQL and Entity Framework
>
>
>http://blogs.msdn.com/adonet/archive/2008/10/29/update-on-linq-to-sql-and-linq-to-entities-roadmap.aspx
>
>I remember hearing of in-fighting last year between LINQ to SQL and the Entity Framework. Supposedly the latter won (no links folks, just hear-say).
>
>This blog is VERY interesting:
>
>http://reddevnews.com/news/devnews/article.aspx?editorialsid=1212
>
>
>Heljsberg says LINQ to SQL was handed off to the ADO.NET team, which was in the process of building EF. "Right now we have the two of them sitting out there," he explains.
>
>He's seen the speculation about the future of LINQ to SQL and says communication from the data team about this issue could be better: "I can assure you, it's not dead," says Heljsberg. "We've invested a lot in it and customers have invested a lot in it, and it's not just going to go away."
>
>Still, many saw Mallalieu's words as the death knell for LINQ to SQL. "It's dead as a door knob," says Microsoft Regional Director Stephen Forte, who is chief strategy officer at Telerik Inc. "As long as LINQ to SQL lives under Entity Framework, it's dead. I don't care what anyone says -- even if Bill Gates comes out of retirement and says LINQ to SQL has a healthy future."
>

Then I'm sure you read what Heljsberg said in the paragraph before, that Linq to SQL was written by the C# team before being moved to the more appropriate spot, the data team (ADO.NET). You have to suspect "not invented here" syndrome is part of what is going on in ADO.NET now.