An enterprise ready, low-code Git-based DevOps toolchain that enables all developers to connect, transform and modernize mainframe application with CI/CD automation, integrated developer environments (IDE), AI/ML-based application performance monitoring and visualization dashboards, and automated testing.
N/A
GitHub
Score 9.0 out of 10
N/A
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.
I'm not sure what scenario it would not be suitable for. I have it up all day, though I do use the mainframe emulator to go back to the old 'green screen'. We have tools that we must use there. There is very little I can't do on the workbench. I'm trying to get some of our new developers to use it, as when I'm using it and talking to them on the phone, they don't know what I'm talking about.
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.
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.
We use CA Librarian here, and the workbench doesn't play well with that. I can't view the library my source is in; I have to copy it to a PDS.
I frequently make some copies of files on my own. I do each file at a time. The ability to create a macro to do all of them at once would be nice. Currently, I click the file and click 'copy to', then fill out the info for each file.
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!
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.
- 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.
Support has been amazing compared to Optim. Further, new features are very regular with File-AID - I can't remember the last time Optim had a significant update. File-AID support is very receptive to feature requests and reported bugs, including sending out hotfixes 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.
Optim is more user friendly in how it operates, in my opinion. It's less obtuse to figure out how to extract and mask the data required compared to File-AID. Further, Optim is easier to gather related tables, by far. I do prefer using File-AID via the Topaz GUI much more than using Optim via its GUI. Finally, I personally believe that File-AID is significantly faster to run than Optim - this could be a configuration issue.
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.
I can debug (expeditor) much faster and more efficiently. In fact, I was asked yesterday to run their job through Workbench Expeditor. I can also view data movement much better.
Code analysis lets me give a quicker explanation of what a program may do, as it provides a graphical interface showing processing and data movement.
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.