Mike Terenni said:
x-no-archive: yes
Not to mention another angle to this--what if hackers had responded
sooner? Surely no one would blame XP customers if hackers let loose a
DAY after the patch was made available. So what we have here are
nitwits blaming people based on how long it takes HACKERS to act.
Let's see. One day vs nearly a MONTH. One day is easy to miss, not hear
about it, NOT GET IT HANDED TO YOU. But a month? With it delivered via
Windows Update? With it mentioned on the news? Mentioned in magazines,
online, ???
Let me create the car/brake analogy again so the nitwits can hopefully
follow:
Going to try to follow yourself? I suppose that's where you get your
circular logic.
Suppose you have a car and the brakes have a flaw. A recall
notice gets mailed to you. What if the brakes fail on you the same day
that recall notice arrives in your mailbox? No one in their right mind
could blame you.
True.
If you get the recall notice and IGNORE IT, then YES,
you are a dumbass, but you DO NOT assume responsibility for the presence
of the flaw in the first place! So what we have here are fanboyz
arguing that the car maker isn't at fault just because they mailed that
recall notice. Even though the critical factor was WHEN the
vulnerability chose to rear its ugly head.
For one, spelling with a "z" makes you seem less and less worth listening
to.
Second, NOBODY's blaming the user for the flaw being there in the first
place. Microsoft *should* have checked. Yet - here's the key - *they took
responsibility already and issued a patch.*
To take your analogy further:
The car maker says "There's a problem" and sends out, not just a recall, but
sends a truck to deliver the replacement parts to you, free. They'll even
tow the car to the nearest certified mechanic, free. You JUST have to say
"Yes, fix the breaks, they sent me the parts."
You don't say that. You sit there with the brake parts in your hand, car in
the shop, mechanic standing next to the car ready to go. You then take your
car, put the brake parts in the front seat, drive around for a month -
PASSING THE MECHANIC EVERY DAY FOR THAT MONTH - and eventually the brake
defect WHICH YOU HAD THE PARTS GIVEN TO YOU FOR, and the car DELIVERED TO A
MECHANIC FOR YOU TO GET FIXED, kicks in and wrecks the car.
This is apparently TOO HARD for you to understand.
No, I don't think ANYONE is arguing that if it happened the day the patch
came out, or even within days, they wouldn't blame MS for getting the patch
out earlier.
Yet, you want to try to use this poor example to say "Awww, you didn't
install the patch MS used to FIX THIS PROBLEM A MONTH AGO."
If MS did NOTHING, they'd be the ones responsible. But the problem has had
a fix AVAILABLE. And DELIVERED via Windows Update.
Ideally, the situation we'd have now is that NO ONE would suffer from
this vulnerability in Windoze. Instead, all we'd have is inconvenience
on our hands. So, yes novices and aloof goofballs are paying the price
for their lack of awareness, but MICROSOFT IS STILL THE ONE TO BLAME FOR
THE PRESENCE OF THE PROBLEM IN THE FIRST PLACE!
OK, so if MS did nothing, they'd be responsibile. No kidding.
But now that MS HAS doen something, made the patch easily available,
practically HANDED ti to people with Windows Update (thus TAKING
RESPONSIBILITY for the problem and FIXING it with the application of a
patch,) the fact that people IGNORED it means... Microsoft's responsibile?
Um. No.
You're less and less worthwhile to argue with, since you only want to twist
your so-called logic, blaming Microsoft for not sending somebody out to hold
your ****ing hand, so I leave you with one final word.
*PLONK*
