Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67117
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender)
MIME-Version: 1.0
Sender: kalle.php@gmail.com
In-Reply-To: <CA+p1TcZ=j5J=pSapeXxtruwmbcqtWoKNZoKxdNaFtc0rmCeqPg@mail.gmail.com>
References: <CAOfKkdTjJr3n=2UajJnNTPA6uHa1d__uwOhmi554nCUAb19OtA@mail.gmail.com>
	<slrnkn9utt.g88.dsp@experimentalworks.net>
	<CAOfKkdS+_K21WyAaySgPaT60gOJkN6Ewc87QS+yCD+WapOSM_Q@mail.gmail.com>
	<CAOfKkdSMZnC6azGSnpM_9NmaQp3A+tPA18CnZgLegX-O_2YtkQ@mail.gmail.com>
	<CA+p1TcZ=j5J=pSapeXxtruwmbcqtWoKNZoKxdNaFtc0rmCeqPg@mail.gmail.com>
Date: Wed, 24 Apr 2013 01:35:28 +0200
Message-ID: <CAJW__o0s2pvBOCnaPttyCGfUfCMhzgL2WW+krzza4tLy6Qz+RA@mail.gmail.com>
To: Arpad Ray <arraypad@gmail.com>
Cc: Pierrick Charron <pierrick@adoy.net>, David Soria Parra <dsp@php.net>, Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Re: [VOTE] Removal of curl-wrappers
From: kalle@php.net (Kalle Sommer Nielsen)

Hi

2013/4/24 Arpad Ray <arraypad@gmail.com>:
> Hi Pierrick,
>
> Why the big rush? There have been three more votes against removing it in
> PHP 5.5 since your last email yesterday so I don't think closing the vote
> early is warranted, but I'm in general confused about the rush to do this
> in PHP 5.5 anyway.

We still have 75% vs 25% on that vote if you account for those new
votes, doesn't make much of a difference (like on the ZO+ vote). That
it is a rush was favored by the RMs to get it removed prior RC stage
to follow our release schedule.

> In principle I'm in favour of moving it to PECL until it's stable, but
> since it's part of the core already and not causing active harm I really
> don't see why that can't wait until PHP.next, and we use the interim to
> warn/educate users.

I in all honestly doubt anyone is gonna work actively on that when its
moved to PECL, same as some of the extensions we in early versions
moved to PECL to have releases there but never had any, but it would
be nice indeed if someone did.

No matter how much we advertise it in our manual, or even front page
news, its limited in terms of far it will reach, and the only action
to take against removing such "harm" as a buggy feature can cause is
far better off to be removed as nobody will see our big red box saying
"Don't enable this in production". I personally would consider the use
of enabling the cURL wrapper(s) the same as enabling safe_mode in 5.3,
its things you "simply do not do" but our userbase does it anyway
since we grant them the ability to do so and the only way to stop that
is to make a stand and remove it if its not fixed. Now I do realize
that removing something is a temporary fix, but in this case its an
experimental feature.

> I think the decision to remove a feature so late in the release process
> should err heavily on the side of caution, and this process has been quite
> the opposite. (Is a 6-line RFC a record? ;)

What more do you want than a 6 liner (its actually 7 including the
patch link) RFC, it goes straight to the point.

-- 
regards,

Kalle Sommer Nielsen
kalle@php.net