Nice and notice how extension methods makes code look conspicuously like it is written in the style of F# code using the |> operator, that is data is pushed into functions left to right - so it looks like a pipeline. I like that.
Do you have more real-life examples of when LINQ is bad? Recently there has been some attention given to the fact that LINQ interacts poorly with impure functions. That would be one example where you have to be careful of using LINQ. The example used looks redundant but otherwise not harmful.
I'm not sure I buy the performance criticism of using LINQ everywhere, in particular since LINQ should be very amenable to analysis since it is exactly the kind of pure code (sans interactions with impure code) that lead languages such as Haskell to be radically and freely optimizable in ways which are becomming increasingly important. Of course in code that is extremely performance sensitive I would probably not use it - but then again I'd probably not even use the CLR to begin with.
Channel 10: Black Friday Deals on Windows 7 Machines
ASP.NET: Presenting in Europe Next Week
WindowsClient: You know your post rate has gone down...
Silverlight: Geek Profiles – Scott Guthrie
