wrote in message news:56dbfdb5.1010...@fleshgrinder.com...
On 3/6/2016 7:07 AM, Stephen Coakley wrote:
<snip>
@Tony Marston: you are always saying that "this is "longevity" [...] they will move on to another language" but I do not see such a language, not a single one. There are those who break with every release (node.js), those who break hard with a major release (Python), and those who are carefully crafted to contain proper CHANGELOGs, upgrade paths, deprecations, ... (Java, C derivatives) and then there is PHP where it is completely random based on the people who saw the actual thread on the mailing list and shouted the loudest.
Just because YOU have not encountered such languages does not mean that they do not exist. Before using PHP I used two other languages for over a decade each, and both of them went through several upgrades which added new functionality WITHOUT breaking existing functionality. That takes brains and discipline, something which appears to be lacking in the PHP community.
Some of us write enterprise software which is expected to last for a long time, not toy websites which are built with the expectation "use once then throw away and start again". Enterprise applications have very large code bases, and it would be a VERY expensive and time consuming exercise to perform a major rewrite with every major release of the language.
I do not mind new features being added to the language provided that I am not forced to use them. I do not mind old features being removed because of genuine security issues. But I *DO* mind having to refactor my code just because some numpty decides to remove a long-standing feature just because it does not fit in with today's fashion. Excuses such as "it's redundant" or "it's inconsistent" or "I don't use it, and I don't think that anyone else should use it" are unacceptable.
Leaving old features alone does not cost anything. Taking them out will take effort, both in changing the code and updating the documentation as well as the ENORMOUS effort required in userland to update their software. This will achieve nothing except to piss a lot of people off.
Removing old or bad features is absolutely normal
Bad features, Yes. Old features, No.
and it is what is being done in good languages.
That depends on your definition of a "good" language. If you look at the language statistics you will see that PHP, with all its quirks, has been in the top ten for a very long time. Changing it now will not be an improvement to many programmers, it will be a disaster and a reason not to upgrade.
You want to keep your interfaces clean and easy to understand. You do not want them to be cluttered with unnecessary features, aliases, argument swapping, ...
Competent programmers have managed with the quirks in PHP for decades, just like they have managed with the quirks which exist in every other language.
Expecting to write some code without any kind of maintenance while expecting the systems and software to ensure it runs for the next decades without any kind of issues is naive.
No it is not. This was the standard for all the other languages I used before PHP. Mind you, those languages were maintained by groups of competent professionals and not an army of chimpanzees.
-- Tony Marston -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
