On 08/03/16 10:12, Tony Marston wrote: > > The only thing I am learning here is that there are too many cooks > spoiling the broth. There are too many people who want to change the > language into something it was not meant to be. There are too many > people who have this notion of language "purity" and "perfection" and > want to force their personal views on the whole of the PHP development > community. They don't care about all those BC breaks which prevent the > quick take-up of new versions. > > When large organisations invest in their software applications they > expect stability and longevity. By creating BC breaks with every new > version of the language you are destroying those expectations and > sending a message to millions of developers "Don't bother using this > language as what you write today won't work in 5 year's time".
I've been providing a caller management system since the early 90's. The JOB it does has not changed in 20+ years, although the reports have changed over time. This was originally based on proprietary terminals ... PC's were not something you found out on the counters then. As that changed, these were replaced with a PHP based application and became web based. Still doing exactly the same job. That job has not changed even today, but some sites that have introduced 'improvements' such as virtual desktops and thin client devices have made the job more and more difficult. One site can't even tell me which building a user is working from because the system does not identity the physical hardware. Fortunately the 'older' services still work so one can at least bypass it and retain the location information, but they have invested too much to admit the real mistake! Problems like this get missed when 'improving services' goes blindly down a particular path, and PHP seems to be stuck in such a rut with new features like Reflections, Traits, magic functions and so on when the vast majority of current applications simply don't need to be changed at all. I'm once again going through perfectly functional code to clear up warnings are now appearing on a server I though HAD all been brought up to be PhP5.5 clean. And I know I'll have to do the same exercise again later for PHP7. Don't say "Just switch off the warnings" ... THAT is what has built up the backlog of work from PHP5.2 ... so adding even more warnings is not helping improve PHP ... -- 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
