basskisser wrote:

On Mar 7, 5:14 pm, "JimH" wrote:

"JoeSpareBedroom" wrote in message

news





"Methanogenesis" wrote in message
...

On Wed, 07 Mar 2007 22:04:43 GMT, "JoeSpareBedroom"
wrote:

"Methanogenesis" wrote in message
om...

On Wed, 07 Mar 2007 20:53:11 GMT, "JoeSpareBedroom"
wrote:

"Methanogenesis" wrote in message
news:s49uu2hvuj1u26s9ode55eunet0pc2ibvc@4ax .com...

On Wed, 07 Mar 2007 20:41:56 GMT, "JoeSpareBedroom"
wrote:

"Methanogenesis" wrote in message
news:ld8uu2pd294k0a61bnt4qb0b90o2gq7as1@4 ax.com...

On Wed, 07 Mar 2007 20:11:47 GMT, "JoeSpareBedroom"
wrote:

"Harry Krause" wrote in message
...

D.Duck wrote:

"Harry Krause" wrote in message
et...

JimH wrote:

http://tinyurl.com/25bo2s

http://tech.yahoo.com/blogs/null/184...o-microsoft-re...

It looks like folks are not too happy with Vista.

I like it. The only problem I've had is that there is no driver
for
my
ancient scanner. So I hooked it up to my laptop, which runs
Windows
2000.

Have you found anything in Vista that would make it a really
compelling
choice of XP?

Vista seems a bit more robust in that when you do something
stupid
and
stall out a program, the computer locks up less and you don't
have
to
do
a
hard reboot.

Any software that locks up because of something the user did should
be
discarded. It's junk and its programmer was an idiot.

Once again, Joe Groceryboy enters the fray with his broad based
opinions on all things idiotic. It's almost like Joe has a PhD in
Idiocy andIinformed Choice.

It's like if the end user doesn't read the manual, does something
that
the computer can't do and it's the programmer's fault.

Tell me all you know about trapping for errors in software. I've got
30
seconds. That should be plenty.

You first. I've got 5 seconds - time to spare.

I know that all errors can be trapped, unless the software isn't ready
for
release yet.

Time's up - you lose.

OK. Give me an example of an actual piece of retail software that crashes
when a user does something. And, tell me why you think that's acceptable
and
why a programmer could not trap for the possibility of the user making
the
product crash.

Nope - time's up.

You lose.

In other words, you're saying that even when a programmer knows what makes
his program crash, it's OK to leave the defect in place.

You lose.

Is Walter Irvin your father?- Hide quoted text -



Maybe it's Dennis Compton?



Interesting that you chose to jump in at this point, Walter.