Thursday, March 11, 2004

Yukon, Whidbey Releases Slip Yet Again

Typical Microsoft crap. How is it that a company sitting on $61 billion in cash and equivalent short-term assets can't get its act together well enough to meet schedules it gets to set for itself? If any more proof were needed that Microsoft is a monopoly, here it is. Any company with a healthy respect for the marketplace would do a better job of getting new products out the door than Redmond has done.

The wait for the long-awaited Yukon and Whidbey is going to be longer still, eWEEK.com has learned. Microsoft Corp. Director of Product Management for SQL Server Tom Rizzo confirmed that Microsoft expects to ship both Yukon—Microsoft's code name for the next major update of its SQL Server database—and Whidbey—the coming update of Visual Studio—in the first half of 2005. In the meantime, a third beta has been added to the current beta schedule of Yukon, with 15 beta customers from across all major vertical industries signing up to run Yukon Beta 3 live in production settings before giving the thumbs up for Microsoft to make the product generally available.

Rizzo also confirmed that rumors about the final names for the products, gleaned from leaked screenshots, are correct: The final name for Yukon is SQL Server 2005, and the final name for Whidbey is Visual Studio 2005. According to Rizzo, both products are on the same timeframe for shipping for a key reason: Namely, Microsoft wants to release the best of its developer tools with the best of its database technology "to really change the industry," he said. "If you look at Oracle [Corp.] and IBM and other competitors in the open-source space, they don't have releases where new and innovative tools are released with a new and innovative database. Customers want that: the next generation of tools that exploit the next generation of database technology." (emphasis added)

The hell we do! This has absolutely nothing to do with what costumers "want," and everything to do with Microsoft's inability to abide by the discipline of deadlines. To hell with this rubbish, I say, and to hell with ASP.NET! Microsoft has messed me around for too long, and I'm not going to wait until 2005 - or, given Microsoft's way of letting deadlines slip, 2006 - to get my hands on standards-compliant web development tools. From now on, I'm sticking with Java.