GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
$4
per month per user
Perforce Helix Core
Score 6.3 out of 10
N/A
Multinational company Perforce, headquartered in Alameda, California offers a version control and peer code review solution. Perforce version control is built around Helix Core with add-on products for code review (Helix Swarm) for free, and add Git support products (Helix4Git and Helix TeamHub). The original Perforce SCM solution was expanded via the Surround SCM, a software configuration management application which was developed by Seapine Software and now owned by Perforce since that…
N/A
Pricing
GitHub
Perforce Helix Core
Editions & Modules
Team
$40
per year per user
Enterprise
$210
per year per user
No answers on this topic
Offerings
Pricing Offerings
GitHub
Perforce Helix Core
Free Trial
Yes
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
GitHub
Perforce Helix Core
Considered Both Products
GitHub
Verified User
Engineer
Chose GitHub
The branches in Perforce and SVN are replicas instead of links/trees like in Github. Those two tools do not have rich APIs like that of GitHub. Subversion and Perforce do not support local repositories, which might hamper the development, if developer is coding and the tools …
I find GitHub more user-friendly; code is much cleaner and it can be integrated with CICD and code pipeline which makes the release process much smoother and faster.
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 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 …
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.
GitHub is well suited for software development, GitHub is particularly well suited for software development projects, where teams need to collaborate on code, track changes, and review code changes. Also for open-source projects, GitHub is an ideal platform for open-source projects, where teams of developers from all over the world can collaborate on code and contribute to projects. For documentation, GitHub provides a platform for creating and sharing documentation, making it an ideal solution for teams that need to create and maintain documentation. On small and medium-sized teams GitHub is well suited as those teams that need to collaborate on software projects and track changes to their code.
While Perforce Helix is the best version control software out there, it can also be used to track your documentation, training videos and materials, and requirements. If you have strict compliance requirements, it can be used to ensure that those requirements are satisfied. Perforce Helix is incredibly flexible and can meet the needs of individual users as well as companies with thousands of users.
As a repository it's great. It houses almost all the open-source applications/code that anyone can fork and play with. A huge collection of sample codes available with problem statements across different domains make Github a one-stop location.
I use GitHub with Windows and the Git Bash is superb. It [is] a powerful alternative to the Command Prompt and Powershell. Allows me to run shell scripts and UNIX commands inside the terminal [on] a Windows PC.
GitHub integration with almost all cloud development/deployment platforms is amazing. Deploying a new application in Azure is really smooth. Just link the GitHub repositories and it's good to go. From automatic build to deployment everything is just amazing.
The branching mechanisms in Perforce allow for an enormous codebase to be duplicated into release versions weekly with little impact upon things such as the speed of queries against the version control.
Action triggers permit such things as automated builds of software versions, dynamic messaging when issues are identified either within or prior to a build process, and much more.
Locking provides the ability to prevent modifications of stable, tested versions in order to ensure validity when they are released.
When browsing history of a file, GitHub could make it easier to see the file after a particular commit instead of just being able to quickly view the commit. I'd like to be able to see the commit or the file itself in one click.
I would like to be able to view commits by user.
I would love to be able to traverse code on GitHub (go to definition, etc) - the good news here is that they are working on these features!
Perforce tends to feel backwards in how it approaches certain tasks, like branching and integrating - even once you figure out how it wants you to perform these tasks, you will likely forget when it comes around to the next time you need to do them again.
Perforce has a higher price tag, comparatively.
Perforce make some tasks very easy, and yet other tasks very difficult - it doesn't always seem to have found its target user's proficiency.
GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.
We are fully committed to our use of Perforce. It works well within our organization and our desire to share our code base with our customers. Their support staff are responsive, inquisitive, and eager to improve their software. I feel like we have a direct line to their design/feature team as they often solicit our feedback.
- Easy to use compared to other version control software. UI interface makes it easy to use, as well as protects against making a major mistake by deleting code, etc. - UI looks modern. - Support for multiple platforms, which I assume will only get better with time. - Student benefits are awesome! - The size limitations on their repositories make sense to me. Not too crazy but realistic from a business perspective.
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.
It's a testament to how easy it is to use GitHub and how many others use it that you can pretty much find the answer to any problem you have by searching online. Consequently, I've never needed to use their support. It's an incredibly easy tool to set up initially, so it won't require much onboarding expertise to get started.
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.
At the time to evaluation - Bitbucket was very tightly integrated into Atlassian’s suite of tools. For an organization that is starting out and looking to spend limited funds effectively - the cost/benefit of using that suite of tools usually doesn’t make sense. Granted things may have changed since then (its been over 5 years) - but at the time GitHub was effective - and all prospective engineers knew about it and already had accounts. This made it very easy to add to the organization and not lose time in training, etc. Developers seem to really love GitHub above most other tools out there - so that plays into the decision making as well.
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.
Github has increased our rate of code development, increasing our publishing rate. This helps bring attention to the research we are doing and ultimately brings in more funding for further research.
Because GitHub makes my team more efficient, we are able to put more hours into code development / report writing rather than agonizing over different versions of code created without version control software.
We use a paid version of GitHub, because we work through private repositories, but the increase in productivity, efficiency, and research progress is definitely worth the price.
