Delayed Yukon, Whidbey

Do you see any opportunities in the fact that Microsofts next-generation tooling and database technology has been pushed back again? Well, I think any time you have a competitor that is promising things and then delays them, you have an effect upon customers who have expectations to get the technology. Microsoft has a long history of promising and not delivering. For many people at this point they listen to all these promises of delivery, and theyre really not paying a lot of attention. Theyll look at it when it finally arrives. I dont think the market is waiting for Microsoft on anything. Click here to read about the delay of "Yukon" and "Whidbey." Were still waiting for Cairo. And were waiting for Yukon and Whidbey and Longhorn and Indigo, and, and, and … the list goes on and on. These things will come when they come. I dont see customers pausing or stopping to make decisions because Microsoft is delaying deliveries. Theyll see what the technology does when it arrives. When it goes on and on you sort of wonder why… They must think that the world is waiting for them to do something. Its like the anticipated release of the next blockbuster movie and people are lined up around the block in sleeping bags waiting to by their tickets. I dont think it works that way. Users could care less about "Yukons" lateness, as long as it ships stable and secure, writes Database Center Editor Lisa Vaas. Click here to read more. Its a technique that Microsoft uses. They must think that its a good technique. I have different views, I dont operate that way. Usually when things finally arrive from them its something thats not exactly what they originally promised. When youre announcing things three years in advance, do you really know what its going to be three years in advance? Next page: IBM vs. Sun and the ongoing debate over open-sourcing Java.