From Microsoft Watch: Yukon and Whidbey have slipped to 2005, Microsoft is confirming. This is more than just another date slip, folks. This is a big one, with big ramifications for Microsoft's suite of current and future product lines. Check out our take on the domino effect of Microsoft's date slips here. [via The Domino Effect (Microsoft Watch)]
Ouch, from all the blogging activity around Whidbey one would have expected it to make it this year - its beginning to make all that blogging and MSDN articles about you can do this that and the other look really pointless. And Whidbey is surely an important release for many reasons, that it has slipped to one years time has a big impact (no .NET 2 and no click-once etc for at least another year).
Worse still is the analysed knock on effects (the domino effect of Microsoft's date slips here.) on Longhorn etc - if Longhorn is now 2007 what the flippin' heck are those guys bloggin' about - some of us have work to do.
Some time ago Mr Scoble recommended I develop a business model to write compelling Longhorn Apps (sorry I've lost the ref) - as usual, never follow the advice of MS that are dependent on release dates. There may have been a PDC, there may have been bits shipped, but this is getting precious close to vapourware.
Rob Relyea commented here that:
Next they are discussing ways to make accesskey simpler as well - still in design discussions. Thanks for bringing this up.
Goodness knows what the next set of bits will look like then and though current code may be compatible, you've probably wasted your time writing it.
Hey, if you want to write stuff now for delivery over the web, is flexible, cute, small and generally rather good - take a look at Zeepe (it does great printing via ScriptX/MaxiPT as well)