Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125845
Feedback-ID: i8414410d:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Thu, 24 Oct 2024 01:25:08 -0500
To: "php internals" <internals@lists.php.net>
Message-ID: <b81465f5-2234-4e79-b25b-8e436da82694@app.fastmail.com>
In-Reply-To: 
 <CAO__Xv4nyrZLRm9ROUQUHAHtsPOSszo5uFx4rZf4WzS8njTGCQ@mail.gmail.com>
References: <92b537ac-62f4-435c-bf55-07223cfa1915@app.fastmail.com>
 <CAO__Xv4nyrZLRm9ROUQUHAHtsPOSszo5uFx4rZf4WzS8njTGCQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Policy on 3rd party code
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: larry@garfieldtech.com ("Larry Garfield")

On Wed, Oct 23, 2024, at 6:57 PM, fennic log wrote:

> I remember a while ago a discussion about bundling composer with PHP by 
> default (and possibly dropping pear).
> What ever happened with that?
> As the first thing any dev does after setting up PHP, is install 
> composer. As this RFC points out, almost every project modern uses 
> composer to manage dependencies, and every Library, SDK and framework 
> requires composer.
> So i'd change this line in the RFC
>>  We should use it, we should document it, we should promote it.
> To
>> We should use it, we should document it, we should promote it, we should bundle it! 
>  
> As I mentioned, it is basically a requirement nowadays to work in PHP 
> unless you are doing something custom that doesnt require any 
> dependencies, but then, is that person planning to release it to the 
> public?
> I am of no opinion of weather php devs internally should use composer, 
> i have no skin in that game. But Documentation - Yes, Promotion - Yes, 
> but does it really need it? Bundle it - Yes!

Bundling Composer with PHP is an entirely different question with a host of additional concerns to consider, like whether the Composer maintainers would even want that.  Let's please stay focused on the topic at hand.

--Larry Garfield