On 07/12/15 12:09, Rowan Collins wrote: > Lester Caine wrote on 07/12/2015 11:47: >> Things are certainly heading in the right direction, but 5.2/3 is still >> only dropped bellow 50% in the last month, while PHP4 was well down when >> the actual EOL was proposed. 80% of people were using PHP5.2 in 2010 >> against 20% on PHP4, and that swung to 90/10 in 2011 mainly because PHP4 >> sites could be switched to PHP5.2 ... switching 5.2/3 sites to PHP7 is >> not so easy, but >> http://w3techs.com/technologies/history_details/pl-php/5/y probably >> shows the best picture, with people migrating to PHP5.4 as the next step >> ... >> > Bundling 5.2 and 5.3 into one bracket seems very odd to me. In my mind, > the major upgrades are 4 to 5, 5.2 to 5.3 (which should have been 6.0), > maybe 5.4 (for things like the call-time pass-by-reference cleanup), > then plain sailing up to 5.6.
PHP5.2 code runs on PHP5.3 with the right configuration of error checking. It is PHP5.4 which replaces the 'deprecated' by removing the code altogether, so in my book PHP5.4 is '6' not 5.3 ... simply hiding problems in PHP5.3 still required that they were fixed at some point! > I would guess that delays in adopting 5.5 and 5.6 are probably more to > do with package availability in enterprise Linux distros (and shared > hosting), and a lack of killer features which people go out of their way > to upgrade for, rather than the difficulty of adapting code. It's > probably actually easier to make the business case for a 7.0 upgrade > than a 5.6 one. Many people adopted the convention of running PHP5.4 in parallel with the PHP5.2/3 servers and certainly in my own portfolio until everything has been moved to PHP5.4 then nothing will move on to a later build. But given the lack of any obvious blockers in PHP7 once all the PHP5.4 code IS running clean, PHP7 seems just as easy a step as PHP5.6 its getting the PHP5.2/3 code past that step which is the current blocker not helped by trying to keep the resulting html code compatible with modern browsers. THAT is another drain on limited resources and detracting from completing other upgrades. I'm not seeing any reports of any particular problems on PHP7. Is that simply because no-one has started testing on legacy code yet, or that the breakages in PHP7 are actually not show stoppers for PHP5.6 code? Certainly I'm not seeing any against my own code, but I still need to complete some work before I can do full speed comparisons against the PHP5.4/eaccelerator setup ... something else that is stuck at PHP5.4. -- 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
