Sdílet prostřednictvím

Whidbey slips - so what?

  • Článek

Good comment by Scott Hanselman on why Whidbey & Yukon RTM slipping to 2005 is not the end of the world ...

I like the quote: "Good, Fast, Cheap. You may choose two."

Comments

  • Anonymous
    March 15, 2004
    I believe fast in that quote refers to performance, not time to market.
  • Anonymous
    March 15, 2004
    The comment has been removed
  • Anonymous
    March 15, 2004
    Frans:

    Yes, I understand that VS.NET 2003 is not perfect, and that there are people out there (incl. you) waiting eagerly for the next version. (Obvoiusly you are not among the people who complain about MS's product cycles being too fast :-) OTOH, we want to ship quality, not as fast as possible (this time ;-). As for "completely unusable", I've heard otherwise from most customers, so this is your very personal (and pointed) opinion. Most of the developers out there haven't even started migrating to .NET. (And it's not because of inferior quality of the current version.)

    We'll have "community drops" and betas pretty soon, so you can start playing with this seriously. And, btw., no tool ever is perfect, so I'm sure it won't take too long after Whidbey RTM that some folks complain that only the next version ("Orcas") will do what they need...

    "So what" means we don't do miracles, so use what's there, and take v.current to the limits (and beyond)...

    :-)
  • Anonymous
    March 15, 2004
    I agree with Frans - I wouldn't mind waiting for Whidbey if they released a service pack to fix some of the asp.net editing issues with VS 2003! You can work around them, its just extremely annoying.. :(
  • Anonymous
    March 15, 2004
    The comment has been removed
  • Anonymous
    March 15, 2004
    The comment has been removed
  • Anonymous
    March 15, 2004
    The comment has been removed
  • Anonymous
    March 15, 2004
    I've been told by MS people flat out the editor will not be fixed before Whidbey. Period. So there you have it.

    Frans... actually, even the drag-and-drop crowd can greatly benefit from Whidbey with all of that declarative programming stuff in the next release. Anything that makes the platform more accessible is good for all of us, especially if it's a jumping off point for them to get into more advanced stuff. The .NET community needs more qualified people, and the way I see it, the more people who get involved the more experienced people we'll eventually have.
  • Anonymous
    March 15, 2004
    The comment has been removed
  • Anonymous
    March 15, 2004
    The comment has been removed
  • Anonymous
    March 15, 2004
    > I like the quote: "Good, Fast, Cheap. You may choose two."

    so is it going to be good and cheap then? How cheap?
  • Anonymous
    March 15, 2004
    Cadmium:

    First of all, you should not call s.o. a liar if you know next to nothing about his/her real motivation. Or can you point to an authorized quote from s.o. from the product team saying that they could fix the designer issue, but won't? Do you really think MS is deliberately selling you inferior software for ... what reason, actually? (Oh, I can hear the Black Helicopters ... ;-)

    Secondly, the Whidbey designer does not have to inherit the VS 2003 code - they could build this on s.th. else (Web Matrix? who knows? just speculating ...)

    Third, there is no official statement saying that this won't be fixed. (Please prove me wrong if you have a KB article or s.th. stating otherwise.) So there's a small possibility for a pre-Whidbey service pack. Even if the probability seems low.

    And finally, let me repeat that sweeping statements like "the ASP.NET designer is virtually useless" do not reflect the true state of the issue, since thousands of developers out there create projects very successfully using this "piece of broken software". You might be frustrated, but not everybody shares this feeling.

    May the source be with you.

    :-)
  • Anonymous
    March 15, 2004
    You have been Taken Out! Thanks for the post.
  • Anonymous
    March 15, 2004
    I feel like a broken record.

    Why is it I am waiting for a new version of VS to fix a bug? Why is this bugfix a 'feature' of the new VS? That's not the worst of it, that bug was in VS.NET 2002! Why wasn't it identified and fixed for VS.NET 2003? I can live with the web controls outputting old html for another year. That designer bug is very annoying, and does make it "virtually useless". Why can I say that? Because you have to avoid it, which makes it a part of the IDE that is not used. You cannot convince me that there are thousands of developers who are conscious to the fact that the designer mangles their html, and still choose to use it.
  • Anonymous
    March 16, 2004
    Has any of those who complain ever reported the designer issue as a bug to PSS? Got a service request (SR) number? I would like to have a look at our internal case database and track this. Thanks.