On 07/09/16 10:58, Rowan Collins wrote: > > If anything, the Composer approach is simpler to deploy, because you can > create a tar ball of the whole project with a populated vendor > directory, and copy it straight to production. (I believe that's > possible with PEAR, too, but not when using the standard shared-library > configuration.) Or you can copy the composer.lock file (probably by > committing to version control) and run "composer install" and get the > same versions you had before without needing to manually go through a > deployment checklist.
I'm still supporting 15+ year old systems and the user manuals are second nature to the users. Changing things requires people to adapt to the change and even subtle changes like run "composer install" can be a problem. Yes we can package everything together, but historically different sites have opted for different options and I doubt that two sites are now using the same set of tools in the background. We can continue to make PEAR work as an option but that means maintaining code that others are improving via different programming styles. This comes down simply to 'education', and just as we provide migration guides to check deprecated code and help re-write it there needs to be the same sort of guideline - provided by PHP - as to how composer or what ever can be used to replace the previous processes. I've seen several examples of how I could be using it, but none that dovetail in with what I have. People who already know composer, as perhaps it's all they have ever used, are at an advantage. I've tried a couple of times to pick up a library that NOW has a composer option, Smarty is a case in point, but IT'S use of composer forces changes to the style of working that are then at odds with the rest of the framework. Yes over a few years I can probably migrate, but this change is adding yet another layer of options without any regard to interoperability. I can't apply a simple set of rules and switch style as everybody else has their own style of using composer? :( -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
