OT: Is Linq to SQL dead

I am noticing a some posts over the last few days saying that L2S might be MS's latest red-headed step child (no offense to anyone :)). My company has made significant investments in WPF and L2S/CSLA. Before the PDC I was worried that desktop WPF would play second fiddle against Sliverlight but after sitting in on the .NET 4.0 sessions I am not worried anymore. I am blindsided about the rumors regarding L2S. We moved from LLBL to Linq because it was simplier and gave us compile time field and type checking. EF seems to be an overkill for what we need. I need a simple DAL. I really don't want to move 500+ BO classes again. Rocky, you have any deeper insight than these blog rumors?

http://codebetter.com/blogs/david.hayden/archive/2008/10/30/linq-to-sql-gets-kicked-to-the-curb-needs-a-good-home.aspx

http://ayende.com/Blog/archive/2008/10/31/microsoft-kills-linq-to-sql.aspx

-Paul

Hmm.. maybe I'm being naive, but saying EF is preferred doesn't mean they aren't going to invest in L2S.  Actually, the original MS post said they would continue to do so. 

L2S has been working really well for me.. it's simple, and even if they don't support it, it seems to handle everything I want.

I love working with L2S.  My only hangup is it is limited to Sql Server.  I wish Oracle would get on the ball.  There are some third party options out there, but you either have to pay for them, or the free one (dblinq) isn't ready for primetime.