Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95769 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60502 invoked from network); 8 Sep 2016 07:49:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Sep 2016 07:49:16 -0000 X-Host-Fingerprint: 90.255.2.72 unknown Received: from [90.255.2.72] ([90.255.2.72:13568] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 58/E0-36123-AF711D75 for ; Thu, 08 Sep 2016 03:49:15 -0400 Message-ID: <58.E0.36123.AF711D75@pb1.pair.com> To: internals@lists.php.net References: In-Reply-To: Date: Thu, 8 Sep 2016 08:49:04 +0100 Lines: 2 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 90.255.2.72 Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle From: TonyMarston@hotmail.com ("Tony Marston") "Michael Morris" wrote in message news:CAEUnE0dfjJ02g2Rhkp9WvnkSXpoLzjK=TMiVDBSuCccgxW2mBw@mail.gmail.com... > >On Wed, Sep 7, 2016 at 3:52 AM, Tony Marston >wrote: >> >> >> Typical. You create a useful tool, get your users hooked, then walk away >> and leave them dangling. >> >> >No one owes you anything. You aren't entitled to get free updates to a free >tool. If the author wants to move onto other projects, that's their >prerogative. Stop with the bombastic and abusive tone towards everyone, >particularly the developers, on this list. Please point out to me any words I have used which a reasonable person would class as "abusive". You may not like what I have to say, but I have the right to say it. I do not like what is being proposed in this RFC, and I have the right to voice my objections. There should be a rule that nothing can be deprecated unless there is a viable, stable, fully functioning and fully supported alternative. I do not like the way that some people simply say "I do not like this. I do not use this. Nobody should be using this. Let's deprecate it" -- Tony Marston