Not the end of the world... not moving it forward either
Scott Hanselman makes the point that the slipped ship date of Yukon and Whidbey is not the end of the world. He's right that, indeed, this is not the end of the world. It's not particularly good for it either.
First of all, Scott, implies that what's good for him is good for everyone because he's shipping product right now. Good for him! He also suggests that “many” of us have a platform that we haven't fully exploited. Tell that to Paul Wilson, who has implemented Whidbey-esque stuff like master pages and ObjectSpaces himself (and is hopefully making a buck or two in the mean time). Heck, I've found an actual verified bug in the framework (which oddly enough still hasn't been documented with a KB article, nearly a year later), so I'm thinking I've gone deep enough with what I have.
If the reason behind the delay was one of development, I might be able to live with that. The now infamous eWeek article, however, seems to indicate that it's not a development issue, but rather one that is purely marketing, pairing the release of Whidbey with Yukon. How annoying is that, when those of us who have acquired Whidbey are impressed with its stability, and pre-beta at that. Members of the .NET team (which have been rather quiet in their blogs lately) have said that they're excited about how clean the first beta will be. That's encouraging.
I guess Scott and those that agree with him either don't use the ASP.NET designer or don't care that it mangles everything you put into it. It's a nightmare for me, because I sell (and giveaway) stuff that people will tweak, hack and change. It gets really hard to support that stuff when VS has messed with what you think they should have.
Make no mistake, I'm not “angry” or anything. My fingers and toes all seem to be intact and the sun did rise this morning, but I still want the product that will make my life easier.