When comparing CodeCompare vs Sublimerge, the Slant community recommends CodeCompare for most people. In the question“What are the best diff tools for Git?” CodeCompare is ranked 9th while Sublimerge is ranked 15th. The most important reason people chose CodeCompare is:
It does not add a blank line in the other code-pane to show where code was added or deleted. It simply draws a line to show point out its location.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Graphical showing of where code is added or removed
It does not add a blank line in the other code-pane to show where code was added or deleted. It simply draws a line to show point out its location.
Pro Three-way comparison and automatic merging
Three comparison panes with horizontal and vertical layouts
- Integrates with version control systems as the merging tool for conflicting file revisions
- Non-conflicting changes are merged automatically
- Merging conflicts are highlighted
- One-click conflict resolution with a mouse button
Pro Supports comparing folders
Can diff entire folders.
Pro Integrated into Visual Studio
Can be used either as a stand-alone product or as the built in diff/merge tool for Visual Studio.
Pro Clear overview that marks only the changes, not every line with a change
Most compare tools mark every changed line with colour, making the code just a mess with thousands of coloured lines, while all that might be changed is a sign/character on each line. Code Compare draws boxes around each changed segment and highlights only the real change with a colour.
Pro Offers free version and paid for version
You get a lot more if you pay for the pro version.
Pro Three-way diff allows easy merging of files
Pro sublimerge
i recommend Sublimerge
Pro Highlights intraline changes
Pro Built-in support for Git, Subversion and Mercurial commands
Sublimerge automatically integrates with your version control history, and lets you compare between revisions, branches, remotes, and the staging area.
Pro Can compare to clipboard contents
Cons
Con No longer supported
Problematic with Visual Studio 2022. Semantic code comparison (its main selling point) does not support newer language variations.
Con Does not support custom comment markings
Some compilers use ";" to specify in-line commenting. But as that is not a common method, all added comments are marked as new code. So it becomes difficult to find changes in the functionality of the code.
Con Does not support move-detection
Very few programs detect move of blocks of code. Most just show deleted and added instead.
Con Free version is limited
Whereas there is a free version, it is missing a lot of great features that you're forced to pay for if you want.
Con Bad tech support
Con It's NOT Open Source
You can't fix or, implement nothing. And when the developer abandons the project you will be left in the lurch.
Con It's not free
Nither as free price nor as free in freedom.
Con Cannot compare text within the same file
Sublimerge can only compare entire file diffs, but not two selections within a file. Comparing within files can be useful for example, by refactoring two similar functions to use a shared function. With Sublimerge, you need to copy the sections into two new temporary tabs and compare between the two. This can be cumbersome, as if you have another untitled file, you won't be able to know which one is which.