Daevid Vincent schreef:
-----Original Message-----
From: Jochem Maas [mailto:jochem@xxxxxxxxxxxxx]
Sent: Thursday, January 31, 2008 8:19 AM
To: richardh@xxxxxxxxxxx
Cc: PHP General List
Subject: Re: PEAR website and MSIE 6
Richard Heyes schreef:
firefox not an option?
Nope.
> or anything else that resembles a proper browser ;-)
Strange, IE has been working fine for me for the last eight years...
Yes. http://pear.php.net crashes my IE6 too. This is a problem with the
site, not the browser.
seriously though - why is FF (or any other browser) not an
option? your
a web developer, I would imagine you should be running a
complete arsenal of
different browsers as part of the job, no?
and then there's the question as to why you don't upgrade to
IE7.
Please stop with the browser wars.
it's not browser wars - it's pragmatism - thinking aloud about how to
get round the issue - I'm assuming Richard does have access to the PEAR site's
source files or the means to upload them to the PEAR webserver.
They're boring and tired and serve no
purpose. IE6 is fast and launches in 1 second. FF takes many seconds. IE7 is
also a bloated pig and I will be very sad in 15 days when M$ FORCES everyone
to it. IE also has very nice DirectX rendering filters for gradients.
or maybe rebuild the windows machine in question (hey it wouldn't be
the first time something
like this was helped by a clean install right?)
It is NOT the OS. It is the PEAR site itself that is to blame. There is
clearly some code or tag or something that is causing this failure.
let's see now - a webserver outputs some content, it may be invalid. a browser
crashes upon trying to render the content. hmm, sounds to me like the problem is
in the browser, decent software should crash because of shitty input.
granted if the PEAR just didn't render properly or caused 'invalid XML/XHTML/whatever'
message in the browser then yes it would be the site's problem. but until the browser
is capable of saying 'hey this content is junk, I can't use it [because of XYZ]' then
really the first issue is with that browser.
it's same at the server end - if your browser (or you, maliciously) posts freaking/invalid
byte sequences at some script I've got on the server then would you consider it correct
that the server crashed? or would you expect some kind of 'your input sucks' error
message to appear?
It
didn't used to be there either. I've gone to the PEAR site many times in the
past. The site isn't even that compex, so I'm curious why the webmaster
couldn't just fix this problem and make everyone happy?
we work around bugs and problems all day in the job we do - how is cranking up a
different browser because a site happens not to work with a particular site any different?
if we're really about making everyone happy - how about we tackle something
serious like the whole 'war for oil' business? exactly how fragile is a human mind if
a browser crashing on a particular site is deciding factor in being capable of
experiencing happiness? (not that I'm suggesting this about Richard - Im sure he
was just a little miffed and ping'ed the question out of curiousity more than anything)
Or is the PHP
community so snobbish that they're turning into the Linux community?
I find it so ironic that all the fringe browser people freak out if their
browser isn't supported by some site and demand retribution, yet when the
tables are turned how quick they are to tell 80% of the world to use a 20%
browser...
let's make it sound like they all *chose* IE shall we - a large majority
of that 80% actually think IE *is* the internet, they certainly didn't choose it
because they thought it was the best tool for the job (which it may or may not
be depending or circumstance and/or perspective) - indoctrination and ignorance
do not make good metrics for determining the superiority of a given product ...
keyboard layout being another fine example ... de facto not necessarily equal da bom
*sigh*
indeed
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
