Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63832
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.125 cause and error)
Message-ID: <50A20CCB.8090909@lsces.co.uk>
Date: Tue, 13 Nov 2012 09:03:07 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120826 Firefox/15.0 SeaMonkey/2.12
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com> <50A10A9D.9070402@oracle.com> <CAAyV7nF2tt6HtFZKevH_2kknqOvEmLJjEOF2_Bn_VHaZFUJERw@mail.gmail.com> <CAPwsocH3_qHSZbLFe27qX+KgBAC1D8KhwLi+PLHW503sCTBtTw@mail.gmail.com> <50A1946F.8010407@lerdorf.com>
In-Reply-To: <50A1946F.8010407@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: lester@lsces.co.uk (Lester Caine)

Rasmus Lerdorf wrote:
> What is true is that most people no longer build PHP at all. They just
> end up with whatever their provider has installed or with whatever
> packages they end up installing when they install the PHP app they want
> to use. Both Wordpress and Drupal depends on php-mysql on Ubuntu, for
> example.
>
> It would be good if we could get the majority of the major PHP apps to
> commit to supporting mysqli along the same timeframe as marking this
> deprecated.

And there is no difference here to getting PHP5.3/4 accepted as the current 
version of PHP? People have working systems and if the number of problems 
changing are too great then they don't change. Rewriting perfectly functional 
mysql code to use mysqli is not a trivial move, just as are the problems of 
re-writing PHP5.2 code to work cleanly on 5.4. ISP's are stuck between keeping 
customers - who are most likely not even very computer literate - working while 
fighting the problems that changes such as removing mysql will cause them.

YES people can simply switch off the checks, but again that misses the whole 
problem! Having switched off the checks - you have no idea what is about to blow 
up. I know people are getting fed up with my banging on about it - I don't have 
any answers - but by removing facilities that perhaps 50% of users rely on CAN 
only be done if there is some concerted effort to help those users who have no 
means of making the changes themselves? Simply saying 'We told you we were doing 
it' is just a kick in the teeth when you have also said 'just hide the errors 
and your old code will still work' - isn't it?

This is not about stopping progress, it's about much better education on how 
that progress should be used ...

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk