Composer is a free and open source dependency manager for PHP. It allows the user to declare the libraries a project depends on and it will manage (install/update) them. it manages packages on a per-project basis, installing them in a directory (e.g. vendor) inside a project and by default, it does not install anything globally. Thus, it is a dependency manager.
N/A
Perforce P4
Score 7.6 out of 10
N/A
Perforce P4 (formerly Helix Core) is the company's version control and peer code review solution. Perforce offers add-on products for code review for free, and Git support products.
N/A
Pricing
Composer
Perforce P4
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Composer
Perforce P4
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Composer
Perforce P4
Considered Both Products
Composer
Verified User
Anonymous
Chose Composer
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 …
In my opinion, Perforce Helix Core is on a top level of irritation and anti-user experience. In my experience, I can't do simple things like 1 word file edits, while I have never been confused when using something based on Git.
Git is great, I love Git. But it's not great for dealing with binary assets, even when using git LFS. Locking is not as simple as on perforce. Git presents some problems on using for non-tech people it can get overwhelming and tech people have to come by and help.
New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that …
My last two jobs used SmartSVN but it required a paid license to use regardless of the number of users. The initial setup for Perforce was much more difficult than SmartSVN. There is a lot of parity between the two software packages even though the terminology can be different. …
Perforce has a better built native visual client that is much simpler to use than Git's. It has a lot of optimizations in the workflow that can execute common patterns during a usual workday. Perforce also has an easier to understand method of presenting merge conflicts and …
Perforce is internally hosted, which makes it quite a bit faster. I found it easier to use that GitHub and Bitbucket, at least in terms of checking out files and creating changelists. GitHub and Bitbucket are much better for smaller teams, as they are cloud hosted, making …
Today's web based software makes them easier to integrate into a development process. Jira with integrated BitBucket as the versioning tool, is ahead of the competition. However for large organizations, Perforce is still a very good choice. GitHub can be used as free tool, but …
Perforce has more features than SVN. However even the simpler tasks in SVN require a degree more technical aptitude with Perforce. Git offers most of the same features, however most of these are only really supported via the command-line in Git, where as most tasks can be …
Perforce is similar to SVN but the SVN has better command line support. Git surpasses both SVN and Perforce because of its flexibility with multiple branches and code review.
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.
For large-scale codebases with fixed and regular releases that do not follow a continuous delivery paradigm, Perforce is certainly well suited. In projects that are small and distinctly separated from other discrete (though potentially dependent) units, the benefits of the Perforce tool may not be as clear of a victor over other systems.
We have a need to consolidate into a single package, and have such a large variety of technical proficiency among our users that Perforce seems less suitable. Many would like to remain using it, however, even those who use Perforce are the minority, and are often limited to our development teams.
With Perforce Helix, you can use it via the command line, via P4V, or any of the other APIs included with the product. It is extremely easy for new users to get up and running. Users of Perforce Helix only have to pull in the files of interest to them. Also, Perforce is very easy to script and integrate into your CI/CD pipeline. Streams allows you to have pinpoint control of your workflow, and P4Search is the absolute best--I wish Perforce (the company) would talk more about this. It is absolutely fabulous!
In our large environment, Perforce is rarely "down". We have regular maintenance windows and from time to time Perforce can feel a little slow, but its always available. Tech support has always worked with our engineers and IT department to make sure that any real performance or stability issues are addressed quickly.
I had two representatives from Perforce contact me after downloading it but never responded when I had questions. I also had a difficult time finding good training material for getting started. There is a lot of available support material when running into issues, though, because of how many large companies use it.
This rating is related to setting up an environment from an existing Perforce repository. Initial setup of Perforce as the repository for the company was done by a separate team long prior to my inception.
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 ...
New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that requires hours to pull together that would take me less than 30 seconds in Perforce Helix. Large file storage in Bitbucket is clunky and requires you to jump through too many hoops. It's not even something you have to think about with Perforce Helix, as you are only limited by your OS. Perforce Helix is very easy to use even for non-developers. I wouldn't dare ask a non-developer to store their documentation in Bitbucket.
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 ...)
