Re: [RFC] Policy on 3rd party code

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