Beyond Compare from Scooter Software headquartered in Madison is a utility for comparing different version of documents and seeing the differences. It also allows changes to be merged and synchronized.
Beyond Compare is extremely good at the task of comparisons, whether that is text file comparisons or folder comparisons. It does a great job of easily highlighting the differences for users, and giving them the option of merging (in the case of text files) or synchronizing (in the case of folders.) In either case, no one on my team has ever had any reason to reach for another different tool.
GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
For date formatting discrepancies the software does not automatically mark the dates as equivalent; for instance ‘2019/10/15’ vs. ‘15-OCT-2019’. This would be considered a difference.
The columns/report must be ordered similarly. If extra data is available in one file, it should be removed or extra rows will be marked as differences.
For spreadsheet comparison, the user must save the file on the proper tab and then “recompare” within the tool. There is no way to switch between sheets in the software.
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
Again, given the intuitive nature of this program, there is barely any learning curve needed. It is simple, reliable, accurate, and just one of those tools you always have with you and rarely think about until you don't have it. Then it is a case of OMG what was I thinking? This program is just very easy to use, and that makes it more valuable to me than some of my other software tools that cost significantly more.
I have never needed support for this product other than learning how to use a new feature I was not familiar with. User forums and user groups that have used this product for their own purposes have always sufficed for anything that I needed help using with the product. Some of the features could be a little better outlined, but overall very easy to use.
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
We've tried many: Code Compare, Meld, UltraCompare, and WinMerge. None of them have the depth of features and speed to handle the work we throw at Beyond Compare. The multi-tabbed interface allows us to sync multiple servers at the same time. It understands multiple file types, metadata, and encodings. It's the best tool for the job.
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy. It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
