Re: What MFC Objects Can't be created on the Stack?
Hi Joe,
See below.
Tom
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:h92gd2dd1jgcpein9g0fjf9mhmhngiejf6@4ax.com...
VC.NET 2003 is slow to start up because it wastes an immense amount of
time loading symbol
tables that hardly anyone ever cares about, instead of doing "lazy"
loading and loading
them only if needed. VS6 had a goal of 10 seconds from fix-to-run, but
VS.NET 2003 spends
15-20 seconds just loading symbol tables that are never needed!
FWIW, VS 2005 didn't get any faster. It seems to work better, but it's
certainly not faster and it has occasion to kind of go dark for a few
seconds every now and then.
Editing speed is irrelevant; VS.NET has one of the worst editors embedded
in one of the
worst IDEs of any product ever delivered by anyone at any time, and some
of its
sluggishness deals with the almost-useless Intellisense database
maintenance (IntelliSense
won't be useful until it starts giving complete dropdowns for flag values,
instead of just
saying "UINT flags", which is why I rarely bother to use it. Since I have
to bring up the
documentation anyway, why use a terminally brain-dead editor that can't
even indent
properly?
I use the built in editor almost exclusively, but I think I'm just used to
it and don't know any better.
The rest of the concerns (security, large distributable, etc.) remain
serious problems.
Indeed.
I agree: hype and coolness now rule at Microsoft, and user-friendliness,
usability,
retraining efforts, etc. are taking a poor second to the advocates of
"cool".
joe
Microsoft didn't invent coolness or hype, but they certainly have cornered
the market on skill of use. Of course, that works to all of our benefit
from time to time.