When comparing Gogs vs Kdiff3, the Slant community recommends Kdiff3 for most people. In the question“What are the best merge applications for Git?” Kdiff3 is ranked 3rd while Gogs is ranked 14th. The most important reason people chose Kdiff3 is:
For modern version control systems, 3way merge support is a basic requirement, but many other open source diff viewers do not adequately handle 3way merges.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Self-hosted
Pro Very light
Gogs is very light and has very low minimal requirements.
Pro Excellent performance and efficiency
The fact that it's written in Go means that it has excellent performance even with little resources (less RAM for example).
Pro Simple installation
The installation process is very simple, just a binary file that needs to be run on the directory where the user wants to install Gogs
Pro Open Source
Distributed under the MIT license.
Pro Cross-platform compatibility
Gogs is written in Go, this means that Gogs can be run anywhere that Go can compile. Be it Linux, Windows or OSX.
Pro Supports 3 way merges
For modern version control systems, 3way merge support is a basic requirement, but many other open source diff viewers do not adequately handle 3way merges.
Pro Free and open source
KDiff3 is completely free to download and use. It's also open source released under the GPL.
Pro Can compare directories
It is able to compare whole directory trees.
Pro Supports editing files directly
In addition to comparing two files it also allows you to edit the merge result right in place.
Pro Diff by character not by lines
On comparing two files, difference is shown by characters; not by lines.
Pro The UI is customizable
Allow customizing colors regardless of user/system theme.
Pro Supports manual code aligning
With selecting code in one window and hitting Ctrl+Y, then selecting some other code in second window and also hitting Ctrl+Y you can manually align the code.
Pro Preprocessing before calculating differences
There are options that may pre-process compared files before Kdiff3 actually do a comparison - to ignore for example automatically generated dates and/or revision numbers added by commit hooks.
Pro Context menu shortcut
You can right-click a folder/file and the options:
- Save <file> for later
- Compare with
will be available, making launching KDiff3 really convenient.
Cons
Con Only one maintainer
The project is driven by only one maintainer. The development will stop if he for some reason stops supporting the project.
Con Can not make pull requests between branches of forked repositories
Con No third party provider support
Con Can't filter by a user to see all their commits in one place
I want to see a single user's entire history, but clicking a user's name only shows all users' history, not just the one I clicked.
Con Supports only git
Gogs supports only the Git management system.
Con Cannot do inline diffs
Comparison of 2 files is always side-by-side and there's no option for inline views. Overall a rather poor and confusing UI in general.
Con Confusing GUI
4 sub-windows (when you really only need 3), a lot of different colors and even more confusing result-window. No links what has changed between versions and and the result. It clearly shows it's dated or rather outdated. Great if you ever need to do a command line merge, otherwise it sucks.
Con No precise editing of the compared files
Precise work line-after-line is not possible. Only a version after the automated merge-step is editable, but not the two files separately.
Con No longer supported by Homebrew for MacOS
Cannot be installed easily on Mac as of Aug 2019.
Con Problems when files have different number of lines
For example, if you add 3 lines: A, B and C locally but on the other change there are only A and C, Kdiff3 will work out that A was added, then it says that B conflicts with C but adds C again anyway.
Con Slow for large files
Con No image compare
Compare is text based.