On 11/09/16 07:06, Pierre Joye wrote: > On Sep 10, 2016 3:32 PM, "Lester Caine" <les...@lsces.co.uk> wrote: > >> I think I am right in saying Pierre originally needed pickle so that >> PEAR could be dropped in the windows? > > It was not the reason. > > My main motivation is about ease developer work (no information > duplication, wrong version number, binary support out of the box, etc), > allow installation from any sources and provide a packagist for extensions > and kill the need of "package release" and finally make it work with > composer. Pecl is still supported and any pecl package (v2) can be > installed using pecl. > > Right now the majority of extensions are not available via pecl but in > GitHub and a bit on bitbucket. And this tells me that there is a big need > for a composer for extensions.
The CURRENT problem is simply that while composer is the popular option for PHP it's not the only game in town. It's essentially only managing installation on the server while there are several other competing options for managing the same problem on other languages and the overall framework. Managing this problem for the browser end libraries is just as important and that is not an area people seem to be using composer for? Although I have no doubt it could do everything. Javascript libraries don't support it today. https://spring.io/understanding/javascript-package-managers gives a nice overview but misses the minefield of 'pricing' which seems to be ever present these days. Even '/vendor/' implies we pay for everything :( On the theme of modern practices, deciding if you rely on your major elements being sourced from CDN, local host them, or as seems to be preferred by the 'test tools', package them up into a single minimized file. Something that we had working out of the box 10 years ago, but which is currently broken because the packaging tools all use different storage models! node seems to be an 'essential' install these days and is 'centrally' installed on the W10 machine ... along with npm without doing anything special, but 'bower' which sits on top of it seems to be the preferred wrapper for dealing with repositories, automatically combining and compacting the selected library set and so on. PHP even manages to sneak in with an add on for CakePHP. As with most things on the net today, one has to work across several different 'languages' one can't do everything just in PHP, and a common tool set is certainly a good starting point for a newcomer? I would still push Eclipse over one of the PHP centric IDE options simply because it has tools for html, javascrip, css, xml and even C if you do want to dig into the raw code ... all in the one package on Linux, Windows and if you must Mac. -- 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
