When comparing IntelliJ IDEA vs SmartGit, the Slant community recommends SmartGit for most people. In the question“What are the best merge applications for Git?” SmartGit is ranked 3rd while IntelliJ IDEA is ranked 8th. The most important reason people chose SmartGit is:
SmartGit has a rather clean and uncluttered user interface. All the most useful tools and information are displayed at all times or are otherwise just a couple of clicks away. All repositories are displayed in the sidebar and through a tabbed interface you can view various info about a specific repository (files, branches, branch graph, etc). The most used git commands like `pull`, `push`, `sync`, `commit` and `merge` are always available on top.
Ranked in these QuestionsQuestion Ranking
Pro Fast and smart contextual assistance
Uses a fast indexing technique to provide contextual hints (auto-completion, available object members, import suggestions).
On-the-fly code analysis to detect errors and propose refactorization.
Pro Smart refactorings
IDEA places an emphasis in safe refactoring, offering a variety of features to make this possible for a variety of languages.
These features include safe delete, type migration and replacing method code duplicates.
Pro Android support, JavaEE support, etc
A very complete development environment support.
Pro Lots of plugins
Many plugins are available for almost any task a developer may need to cover. Plugins are developed by Jetbrains themselves or by 3rd parties through the SDK available for writing them.
Pro Support for many languages
IntelliJ supports many languages besides Java, some of these are: golang, Scala, Clojure, Groovy, Bash, etc...
Pro Stable and robust
IntelliJ IDEA hardly ever crashes or has any issues that plague other Java IDEs like file corruption or slowness.
Pro Intuitive and slick UI
IDEA has a clean, intuitive interface with some customization available (such as the Darcula theme).
Pro Clear and detailed documentation
The documentation is exhaustive, easy to navigate, and clearly worded.
Pro Free version available
There is a free community edition (open source) and an ultimate edition, which you can compare here.
The ultimate edition is available for free for one year for students but must be registered through an .edu e-mail account.
Pro Very powerful debugger
With ability to step into a certain part of a large method invocation (Shift+F7), drop frame, executing code snippets, showing method return values, etc.
Pro Many convenient features
These simplify the daily work, e.g. copy/cut a whole line without the need to select it.
Pro Uncluttered UI
SmartGit has a rather clean and uncluttered user interface. All the most useful tools and information are displayed at all times or are otherwise just a couple of clicks away.
All repositories are displayed in the sidebar and through a tabbed interface you can view various info about a specific repository (files, branches, branch graph, etc). The most used git commands like
merge are always available on top.
Pro Free for non-commercial use
SmartGit can be used free of charge by Open Source developers, teachers and their students, or for hobby, non-paid usage.
Pro Easy to use
The clean and intuitive UI makes SmartGit very easy even for people with no prior experience with Git, even after reading just a bit on how Git works and what the main commands are.
Pro Supports Git, Mercurial, and SVN
SmartGit supports Git and Mercurial, as well as SVN via git bridge.
Pro Git-flow support
Git-flow provides a consistent development process by defining a strict branching model that is great for managing large projects. SmartGit allows for setting up and integrating into repos that follow this model.
Pro Smart embedded difference viewer
When the changes affect only a few characters in a line of code, the embedded difference viewers in the majority of competitors (such as SourceTree) show the whole line as removed and re-added. SmartGit highlights the characters that have been removed / added, so they are easier to read.
Pro Great view of the timeline of the project (the log)
Pro Auto-detects repositories on disk
Pro Portable version for Windows is available
SmartGit also has a portable bundle that can be downloaded and can be run from external devices (such as a flash drive for example).
Pro GPG support
GPG in SmartGit makes for added security.
Pro Extendable with external tools
External tools (which have a command line support) can be integrated to be used to open/view files, for diff or as conflict solvers. E.g. editors like Notepad++ or VS Code, p4merge to diff images or kdiff3 as diff view/conflict solver.
Pro Best submodule workflow on the market
You can easily update submodules from the containing repo, unlike other GUIs that require you to open each repo separately. Saves a lot of time when working on a monorepo managed using submodules.
Pro Can be integrated with Github, Bitbucket, and Atlassian Stash
Using OAuth, you can connect SmartGit with your accounts in Github, Bitbucket, or Stash and access the remote repositories there. You can then clone, fork, commit or push to your remote repositories from inside SmartGit. You can also view and manage pull requests for your open source projects from SmartGit.
Pro Can rearrange Repository window and Log window views/panels
This allows great layouts as desired.
Pro Can detect issue numbers and links to the issue tracker
Support GitBugTraq file : https://github.com/mstrap/bugtraq
Pro Has the most features and most logical layout
Compared to gitk, git gui, SourceTree, GitKraken.
Pro Syntax coloring for many languages
The built-in compare and conflict solver has syntax coloring with customizable colors.
Pro Great filtering options
The file list view can be tweaked and filtered in many ways (e.g. regex can be used).
Pro Log: ability to see dangling commits and stash commits
Rebased, but not yet garbage-collected commits can be easily made accessible again, e.g. after a reset hard.
Pro Log with fine-grained display of branches
There is no option of just showing the current branch or all branches, but you can select very fine-grained what branches/forks should be displayed.
Pro Auto stash
Greatly improve the user experience when rebasing etc
Pro Great support
Support responds quickly and they genuinely try to help you! If it's a bug, it will often be fixed within days.
Pro Supports selecting open issues from JIRA
Allows you to select the desired issue, instead of having to do it manually.
Pro Every git command is available through the GUI
Not every, but nearly all.
Pro Excellent dark theme
And support for own themes.
Pro Evolution submission program
Pro Allows rearranging views
If screen space is limited, one can stack some views onto another. 2 layouts are available - "Main" and "Review" - with independent view positions.
Pro Journal dedicated for current branch history
Showing commits from the current branch, its remote branch and one auxiliary branch. Independent of the that, there is a log window available that allows to view all (other) commits.
Con Built with closed source components
The version with full features is not opensource. Parts of the code are under apache licence though.
Con Bugs are not solved as often as they should
They are more interested in adding new features or issuing new versions than solving bugs.
Con Slow startup
Con Uses too much RAM
Con Lack of plugins
IntelliJ supports a very small amount of plugins. Althrough thesse are 'quality approved', many features are missing and can't be implemented because of that.
Con Cannot open multiple projects in the same window
Con Standard hotkeys behave differently
Seems like hotkeys assignment in Idea has no logical consistency.
Like «F3» is usually next match, «Ctrl+W» - close tab, etc — they map to some different action by default.
There is a good effort in making the IDE friendly for immigrants from other products: there are options to use hotkeys from Eclipse, and even emacs. But these mappings are very incomplete. And help pages do not take this remapping into account, rather mentioning the standard hotkeys.
So, people coming from other IDEs/editors are doomed to using mouse and context menus (which are rather big and complex).
Con Proprietary license
Not an open source license.
Con External log window
A "Journal" view is available in the main window, though, and focuses on the current branch (incl. remote branch) and one additional ("auxiliary") branch.
Con Some git functionality has been renamed
In order to preserve the same interface across Git and Mercurial, some naming compromises have been made so that the various VCS it supports are all consistent with each other.
Con Perspective views can be limiting
Being able to see everything at a glance is important. Some updates, however, change the perspective views which are rather fixed. It lacks a more open way to add and remove windows to create your own perspectives as these changes between versions can disrupt a nice workflow.