GitHub vs. Python Package Index (CheeseShop) vs. RubyGems.org

GitHub is an easy to go tool when it comes to Version Controlling, CI/CD workflows, Integration with third party softwares. It's effective for any level of CI/CD implementation you would like to. Also the the cost of product is also very competitive and affordable. As of now GitHub lacks capabilities when it comes to detailed project management in comparison to tools like Jira, but overall its value for money.

Incentivized

RubyGems is a great packaging library primarily because of its verbose logging information and easy to navigate system architecture. We've dealt with artifactory systems in the past for Java and JavaScript, and RubyGems just makes it a lot easier to handle the packaging and deployment of our reusable libraries. We've noticed in the past that there are times where (if all 200+ teams) are releasing at a similar time that publishing the gems can lag, but that's fairly rare.

Incentivized

• Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
• Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
• Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.

• Seemless packaging
• Well documented
• Verbose error logs
• Active community support
• Quick security fixes/releases

Incentivized

• Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
• Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
• Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
• While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.

• Lack of solid Windows support.
• Not great performance if lots of people release at the same time.

Incentivized

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.

GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.

Incentivized

There are a ton of resources and tutorials for GitHub online. The sheer number of people who use GitHub ensures that someone has the exact answer you are looking for. The docs on GitHub itself are very thorough as well. You will often find an official doc along with the hundreds of independent tutorials that answers your question, which is unusual for most online services.

Incentivized

RubyGems has strong community support and finding issues to errors is as simple as searching for the error message you're receiving (but usually the error is clear enough without having to bother with that). Honestly, the framework is simple enough that support isn't needed much, but it has been helpful to us in the past when we have needed it.

Incentivized

While I don't have very much experience with these 2 solutions, they're two of the most popular alternatives to GitHub. Bitbucket is from Atlassian, which may make sense for a team that is already using other Atlassian tools like Jira, Confluence, and Trello, as their integration will likely be much tighter. Gitlab on the other hand has a reputation as a very capable GitHub replacement with some features that are not available on GitHub like firewall tools.

Incentivized

RubyGems is easier to use and to troubleshoot issues overall. Sometimes when troubleshooting in other systems errors are masked and it takes a trained eye or a lot of time searching through Google trying to find out what it really means. RubyGems is very verbose and allows for quick troubleshooting of any deployment problems.

Incentivized

• Team collaboration significantly improved as everything is clearly logged and maintained.
• Maintaining a good overview of items will be delivered wrt the roadmap for example.
• Knowledge management and tracking. Over time a lot of tickets, issues and comments are logged. GitHub is a great asset to go back and review why x was y.

Incentivized

• Quick package hosting.
• Faster deployment process.
• Less troubleshooting needed during deployment.

Incentivized