Composer vs. Hackage

It can/must be used for any size of software project. Not only provides the best way to control depencies, but also has a strong worldwide community of developers.

Incentivized

• Controlling dependencies
• Fast dependency resolver
• Easy to use dependency injection

Incentivized

• Sometimes a bit slow, but v2 made a lot of improvements on that
• If everything is modular, setting up a local dev environment is a bit trickier than having everything in the same repo
• Might be hard to adopt with some frameworks which have not fully embraced it, like Wordpress

Incentivized

If you're familiar with npm or Yarn, you'll feel right at home with composer. The work in pretty much the same way. You can use a composer.json file in your repo to reference specific version of public community modules, and enterprise internal ones. You can also hook some scripts that you would want to execute, like for testing, building your code ...

Incentivized

• Helped us reduce the TTM of our ecommerce factory by about 40% since we adopted it
• Code re-usability became the norm, and thus much shorter development cycles
• New websites go live much faster, and thus cost way less money to make when reusing composer modules (SSO, CRM integration, modules to call Internal APIs ...)

Incentivized