Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70824
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFWS2+EpQ_pEfL14P-7wFLWA+JZ3QjUvxH=GbVJ9zGjx9wVjcg@mail.gmail.com>
References: <52B5522A.4040709@lsces.co.uk>
	<52B61756.9090202@gmail.com>
	<52B620D7.6090200@evermeet.cx>
	<CAFWS2+EpQ_pEfL14P-7wFLWA+JZ3QjUvxH=GbVJ9zGjx9wVjcg@mail.gmail.com>
Date: Sat, 21 Dec 2013 17:25:10 -0800
Message-ID: <CAKOpQSx56CNYdZTwib4yo_P5SvvcVtLyR3MXObzPh-1TMTUNdw@mail.gmail.com>
To: Ronald Chmara <ronabop@gmail.com>
Cc: Helmut Tessarek <tessarek@evermeet.cx>, Rowan Collins <rowan.collins@gmail.com>, 
	internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c339e6de986404ee156133
Subject: Re: [PHP-DEV] Censorship in php
From: kris.craig@gmail.com (Kris Craig)

--001a11c339e6de986404ee156133
Content-Type: text/plain; charset=ISO-8859-1

>
>
> Thousands? No, many, many, millions. If you break PHP, you break Yahoo,
> Wikipedia, Wordpress, Facebook.... many millions of sites. Maybe billions
> at this point.
>
>
I don't think he's saying we should "break" PHP.  I think he's saying that
we tend to be overly worried about maintaining BC even on bad
functionality, an assessment that I agree with.  Maintaining BC religiously
on minor increments is understandable.  Breaking BC on a major release
increment is not only ok, I would say it's even expected.  Also keep in
mind that big-timers like Facebook and Yahoo! aren't going to blindly
upgrade to the latest version without first making sure their code is up to
current standards (which they should be doing, anyway).

Relevant:  http://xkcd.com/1172/

--Kris

--001a11c339e6de986404ee156133--