Re: Read this Maccies and be afraid, very afraid

In article <alangbaker-28BCE0.15031220082005@xxxxxxxxxxxxxx>,
Alan Baker <alangbaker@xxxxxxxxx> wrote:

> In article <csseg11lqbq6573jsh68e3th9f9ggvdbb9@xxxxxxx>,
> Josh McKee <jtmckee@xxxxxxxxxxxxxxx> wrote:
>
> > On Sat, 20 Aug 2005 17:11:55 GMT, Alan Baker <alangbaker@xxxxxxxxx>
> > wrote:
> >
> > >In article <cfoeg1t4cokrojd44mu0k9cf4a74untksq@xxxxxxx>,
> > > Josh McKee <jtmckee@xxxxxxxxxxxxxxx> wrote:
> > >
> > >> On Sat, 20 Aug 2005 03:00:52 GMT, Alan Baker <alangbaker@xxxxxxxxx>
> > >> wrote:

> > In some of the cases they're not writing it. The specific instance I
> > am thinking of was a problem in Apache 2.0.52. A problem that was
> > fixed by the open source community almost four months ago. Why did it
> > take Apple almost four months to release a patch for software written
> > by someone else who patched it so long ago?
>
> I don't know. Do you think they were deliberately making things
> difficult for their customers?

No. But that's what Mac zealots appear to think when Microsoft doesn't
release a patch according to their schedule.

> Perhaps there's a little more to it than your simplistic analysis concludes.

I would bet that there is. Unfortunately the Mac zealots don't extend
this thought process to Microsoft. <- That's my point.

> > >Do it too quickly and you get mistakes.
> >
> > You guys are hilarious. Apple takes almost four months to release a
> > security update and you excuse it by saying that they're justified
> > because they want to ensure that the patch doesn't have mistakes. In
> > the meantime that very update is breaking things.
>
> Sure. Sometimes mistakes get through.

Yes. Just as with Microsoft. However when Microsoft does it they're
incompetent idiots who don't know jack about writing software. When
Apple does it it's "a mistake".

> > >> and
> > >>
> > >> "Probably, at a guess, the fact that Apple actually TEST their
> > >> software before releasing it."
> > >>
> > >> I should note that he made that second statement just prior to the
> > >> announcement that Apple's latest security patch broke 64 bit support.
> > >
> > >Yup. Apple made a mistake. And already fixed it, BTW.
> >
> > How can that be? Didn't you just get done telling me that they take
> > their time releasing patches so that they don't make mistakes?
>
> No. I said that they take their time to *try* to eliminate mistakes;

Yet Mac zealots fault Microsoft when they take their time trying to
ensure no mistakes are made.

> to reduce mistakes as far as they can. That doesn't mean that it is going
> to succeed in every case.

Exactly. Mac zealots should keep this in mind the next time they want to
decry that Microsoft is taking to long. Or that Microsoft released a
buggy patch.

> > >> >-- like everyone else in the world -- they make their share of
> > >> >mistakes.
> > >>
> > >> Perhaps you would be so good as to try and convince a Mac advocate of
> > >> this fact. PC advocates have been trying to tell this to Mac advocates
> > >> for quite some time. Unfortunately it's fallen on deaf ears.
> > >
> > >Bull***.
> >
> > Thanks for proving my point.
>
> It has not fallen on deaf ears, because nobody here pretends that Apple
> doesn't make mistakes.

They do everytime the decry Microsoft for taking too long to release a
patch. Or when they decry Microsoft for having released a buggy patch.

Do you happen to see a pattern here? My issue isn't with Apple taking
too long to release patches. Nor is it with them occasionally releasing
buggy patches. It's with the Mac zealots who fault Microsoft for these
reasons while excusing them when Apple does it.

Josh
.