wrote in message news:56daf480.7030...@fleshgrinder.com...
On 3/5/2016 2:33 PM, Lester Caine wrote:
On 05/03/16 11:26, Fleshgrinder wrote:
PHP being a mess is still one of the most quoted arguments against PHP!
But then again, we are talking about removal and real BC in 6 to 9 years
and support for code that is already roughly 11 years old; so up to 20
years old then. I guess nobody would ever consider rewriting that code
and instead simply write it anew.
I will never accept any BC breaks unless it is to solve a genuine security
issue. Saying that it's only going to happen in 6 to 9 years is irrelevant
as it should never happen at all. Saying that code which is 11 years old
should be rewritten is just plain naive. If a language cannot support code
that was written 11 years then that language will be regarded as unstable in
the real world.
One of the most successful pieces of software is an ERP application from SAP
which was started in 1970, and it is still going. Why? Do the maintainers of
that software keep rewriting it every 5 years to keep up with the latest
programming fashion? The answer is "NO". They cannot afford to rewrite their
application every 5 years, and their customers would hate to go through an
expensive upgrade every 5 years. The customers expect longevity and
stability. What you are trying to do to PHP would destroy that, and for NO
GOOD REASON!
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
