Re: cvs: php4 / php.ini-recommended
| From: | Rasmus Lerdorf | Date: | Thu, 26 Sep 2002 14:10:26 +0000 |
| Subject: | Re: cvs: php4 / php.ini-recommended | ||
| References: | 1 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-14251@lists.php.net to get a copy of this message | ||
If Set 1 was truly empty, I'd agree with you.
-Rasmus
On Thu, 26 Sep 2002, Sascha Schumann wrote:
> > My worry is that this change appears to have absolutely no positive
> > aspects and only negative potential. We know browsers exist that cannot
> > handle 4-digit years. Early WebTV boxes don't, early Netscape don't. We
> > do not know of any browsers that cannot handle 2-digit years. Hence I
> > fail to see the upside with this change.
>
> Well, let me restate that pure existance of software does not
> matter. I still have NT 4.0 with a MSIE 2 in the desk -- it
> exists, but you don't design applications for it anymore. It
> is the actual use which counts. For further confirmation of
> this, you just need to look at major web stores such as
> amazon.com. They are not afraid of making the move to
> 4-digit years.
>
> Let us consider two sets
>
> 1: Browsers in use which handle only 2-digit years
> 2: Browsers in use which handle only 4-digit years properly
>
> While both sets may be empty at this time, a safe and natural
> prediction is that the size of the second set will increase.
> The first one will not change and remain at 0 for obvious
> reasons.
>
> And therefore I've introduced this proactive change.
>
> - Sascha
>