Let me be the first (well more like the 50,000th) to say that re-branding WinFX to .NET Framework 3.0 is a STUPID idea. (Yeah that’s right, I bolded it.)
Set aside for a second that it’s a bad representation of the product, there’s already a .NET Framework 3.0 in the works and WinFX isn’t it! WinFX runs under CLR 2.0. They should call it .NET Framework 2.5 or something. WinFX will not include 3.0 features, such as LINQ.
Why, oh why, Microsoft?
WinFX was a cool name, and developers who were confused about the role of .NET in WinFX should just google it and read a tad. It won’t kill you I promise.
/mourns the loss of Indigo, Avalon, and now WinFX in this Microsoft naming wtf’ery
Now playing: Keane - Untitled 1