To MS: Listen to your Customers

Frans and Martin both think this Yukon and Whidbey delay is crap (as does the overwhelming majority of the people that are commenting on their blogs). I agree. MS has been hyping Whidbey, ObjectSpaces, ASP.NET 2.0, etc. for long enough, and now they are telling us that .NET 2.0 won't even come out until the time when we were originally scheduled to recieve .NET 3.0 (Longhorn version). All you MS bloggers out there, NO ONE REALLY WANTS YUKON AND VS.NET INTEGRATION! We want Whitehorse. We want ObjectSpaces. We want ASP.NET 2.0. We want Generics. Save Yukon integration for a minor release in 2005 (like VS.NET 2003).

[1] http://weblogs.asp.net/fbouma/archive/2004/03/11/87836.aspx

[2] http://weblogs.asp.net/Mspedding/archive/2004/03/11/87887.aspx

 

9 Comments

  • Well I *DO* want the Yukon cool stuff....



    BUT I want the .NET 2.0 and Whidbey stuff *SOON*

    I can use SQL 2000 for another year or two as is.

  • +1 - so how can we actually get enough feedback to MS to make a difference? any ideas? Scoble are you reading this?

  • I want Whidbey yesterday, but just to play Microsoft's advocte here...



    If I were to guess, I'd suspect that stripping out the Yukon integration out of Whidbey, testing the changes, and updating the docs would probably delay Whidbey by about as much as waiting for Yukon would.

  • I very seriously doubt that. It's not like Whidbey is built on top of Yukon (not to mention that Whidbey is going to have to work fine with people who have no Yukon installed anyway).

  • Yes, but releasing 8.0, then 8.1 would do the trick. That is what I am suggesting (not 7.2, 8.0). Whidbey has enough new functionality without the Yukon junk to justify a major version increment.

  • Big releases generate revenue from upgrades and new customers. Minor releases don't generate as much. If VS.NET went from 7.1 to 7.2, we'd expect a free upgrade. If it went from 7.x to 8.0, then... Get my drift?

  • If the CLR exists as an entity in its own right, as does the whole .NET Framework and BCL's, as does Yukon, I don't see why the boundaries between these processes have to be all tied together in one full hit release if an IDE. True, most of my apps are DB related, but I have a whole heap of Windows/Web Services etc that could'nt care less about the System.Data namespace. How about a compromise, give us the .NET v.2 SDK ASAP, then we can at least convert some existing apps and get going on the v2 stuff, even if we have to do it in notepad. I always try to protect MS from people throwing mud at them and .NET is a testamant to the brilliance of MS architectual and engineering potential. Seems to me that the money/marketing people at MS are stepping on the toes of the very people in their own company that made MS rocket into the forefront of the development world.

  • I had a chuckle at the part about "free upgrade" from Microsoft. When was the last time THAT happened?


Comments have been disabled for this content.