At 05:24 PM 4/11/00 -0700, you wrote:
> > At 04:06 PM 4/11/00 -0700, you wrote:
> > >Dear Janet (yes, that's a condescending 'Dear')...I've been married to
>the
> > >same woman for 27 years in two more days and I've come to realise that I
> > >can't win arguments with the opposite sex once they've mad up their
>minds.
> >
> > Maybe there's a reason for that.
>
>hmmm...yes, I'll just bet there is ;)
>
> > >My point was that it didn't work with 20,000,00 browsers and my unsaid
>point
> > >was that for a major release they might have done a bit better at beta
> > >testing.
> >
> > You mean like any other software? All software has problems with the first
> > release. I would like you to show me software that was released with no
>
>If this was CF's first release it wouldn't bother me so much...however,
>Allaire had it right in versions 1.5-4.01 and in 4.51...they just flat
>screwed up in 4.5 and I'm not going to be an apologist for them. There are
>NO issues of cross-platform programming. If so then why did it work fine in
>every release UNTIL and AFTER 4.5?
I already told you. I *didn't*. Maybe your issues just appeared but our
issues have been there for a long time. I'm not apologizing for anyone
because it isn't necessary. It's completely understandable.
> > bugs because that would be a world record. Besides which, you are assuming
> > that all AOL users use the browser. I know several people who use AOL for
> > email alone and have a separate ISP for other web activities. AOL has
>
>OK...OK...20 million minus the several you know ;)
Oh the logical flaws...
> > problems because it has so many users and their computers can't keep up.
> > That is why the service is so crippled. Oh, and by the way, a new AOL
> > browser was released a couple of months back. Maybe the code worked on the
> > old browser. Basically, you are getting overly angry about a situation
>that
> > is perfectly natural and understandable.
>
>Well, maybe you're right...maybe I'm just an old cranky fart that needs to
>be put out to pasture...but I did ask my wife this morning if I was
>tolerable and she replied in the affirmative, of course, that was this
>mroning...I might have gone down hill since then ;) ...and BTW, it worked
>WITHIN REASON with ALL AOL browsers from 3.0 on to the latest, just not with
>CF 4.5 and O'Reilly's Website Pro (which BTW was where CF first got it's
>major exposure to the world).
>
> > >In the 'old' days if you did beta tests you were expected to test as
> > >completely as you could and in exchange for that, the company would issue
> > >you one of the first releases for free. The last I looked at Allaire's
> > >policy on this (and I might be wrong...if I remember, I was wrong once)
> >
> > I've counted more times than that, today alone.
>;)
> > > was
> > >that the beta was open to it's 'Subcribing customers' (which doesn't
>count
> > >as snot as they already have a year's worth of software coming to them)
>and
> > >that in the later stages they release it to the public at large, of
>course,
> > >with no free issuances.
> > >
> > >I'm still doing beta testing for some of the companies that supply
> > >components for Visual Basic and when one of these components hits the
>market
> > >you can be darn sure that they'll work with nearly every VB compiler out
> > >there ;) That's the difference between being a popular company and and
> > >excellent company.
> >
> > Oh really? Have you ever tried compiling C in multiple compilers? I dare
>you.
>
>You dare me?...how dare you ;)...and not for several years...gave it up
>because of what you mention...too damned hard to do...besides, why would I
>want to program in C when I can much more productive in VB...if I were
>writing code for hardware then you might have a point but even for that I'll
>use Forth or Pascal
>
> > Besides which, CFServer is sort of like a compiler, so by your theory, you
> > should be able to use CFML with CFServer and lo and behold... you have
>your
> > wish
>
>Well lo AND behold...I've been doing that since release 1.5 and my wishes
>have come true (EXCEPT [here comes the hard part] in version 4.5)
>
> > However, making things cross-browser compliant is a different story.
>
>You're absolutely right...and it doesn't belong in this story because it
>isn't an issue...all of our sites worked fine with AOL BEFORE AND AFTER CF
>4.5 so tell me where cross-platform browser compliancy enters the equation?
>You can't because it doesn't.
>
> > There is a standard for VisualBasic and for your code to compile properly
> > in any compiler that compiler (and your code) has to follow the standards.
> > Otherwise, its all accommodating this little quirk and that little quirk.
> > There is a standard for browsers and none of the browsers use it. AOL's
> > browser is amazingly far from the standard and thus, the code won't work
>on
>
>It worked for people using 4.5 and not using O'Reilly's Website Pro...I
>always thought that the right thing to do was to 'dance with the one that
>brung ya'
>
> > it. So your example supports my theory and not your own. AOL should use
>the
> > standards for browsers instead of blatantly ignoring them. Then this would
> > never have been an issue.
>
>The only thing I haven't been able to code around is Mac users trying to
>upload JPEGs without their MIME types set on the client machine...sorry, I
>can't do that from here, at least not until after I catch the error and by
>then it's too late...the file is already here ;)
>
> > Man. You really are bitter today, aren't you? I think it's about Beer:30
>in
> > your time-zone.
>
>(grin)...beer:30 left my life several decades ago
>
>------------------------------------------------------------------------------
>Archives: http://www.eGroups.com/list/cf-talk
>To Unsubscribe visit
>http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
>send a message to [EMAIL PROTECTED] with 'unsubscribe' in
>the body.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
