Move forward with Composer

Presentation I gave at Exeter Web on how PHP developers should be moving forward using Composer

Transcript

2. ⚠ Bold statement alert!
3. The most important change in the PHP community * * For me anyway
4. Composer = Dependency Management ... mail log database 0.7.1 dev-master 1.2.*
5. Other languages have nice things Bundler Pip Insert a million others here While we had PEAR Good luck getting a package accepted pear/Mail last released 2010 Your running 3.6.12, well I’m running 3.7.2
6. Composer brings lots of benefits Everyone uses the same dependencies Generates an autoloader Keep your project up to date Massive amounts of code on Packagist
7. Libraries Guzzle Swiftmailer ... Frameworks Symfony Laravel ... Tools PHPUnit Phing ... something like 11,000 packages
8. How many times have you created Database Logging Authentication ...
9. STOP this MADNESS! ⛔
10. I’m happier shipping than building boiler code
11. Why build an API on a bloated framework just because you like its query builder Pull out the parts you want
12. Don’t wait for 2.* release when the ORM has changed already Router Twig
13. PHP is growing up Object model Standards Toolset
14. Packages have tests Properly versioned Maintained Quality of code on the up Ruby, Python etc communities already (mostly) do this when they release code
15. checkout getcomposer.org checkout packagist.org
16. @vivalacrowe  ✉  @rcrowe hello@vivalacrowe.com
17. ❓