"lover" <microsoft rulez!> wrote:
a GUARDED look toward the future:
VS.Net 2002 had all these bugs;
VS.Net 2003 failed to fix them;
2004 will probably claim to fix them but fail;
by the time 2005 rolls around, there's probably a 50/50 chance of it
working right... (don't hold your breath)
It's sad that Microsoft has put quality control on the back burner. VS.NET
2003 was a major disappointment with so many problems unaddressed (and new
ones added), and no service packs. I imagine that if the Visual
Studio problems got as much bad press as the security problems, they'd be
addressed, if only to "put out the fire". But since they don't, it seems MS
just isn't going to put any extra effort into addressing them.
BTW, I am convinced this is NOT a decision by the tech guys at Microsoft.
Most developers I've worked with hate the idea of having their bugs go out
to the public. (OTOH, maybe when the number of developers gets that large,
you lose any sense of individuality or responsibility). I suspect it's a
conscious marketing/management decision. After all, service packs and bug
fixes provide no income, and we'll all come back next year to upgrade
anyway, right? I can't come up with any other explanation that makes sense
(and believe me, I've pondered it many times, such as each time VS.NET
crashes or some other feature isn't working again).
--
harry
(Now Playing: Teilmenge 25A - Asmus Tietchens)