WebStorm vs SmartGit

WebStorm integrates with Node.js to allow for running, debugging, and unit testing of Node.js apps.

To make sure your code can be easily maintained, you must first be sure to make it clean and tidy. This is the part where WebStorm really helps you. It automatically refactors your code by performing functions on it, such as extraction of variables, moving files, inline variable extraction, etc.

WebStorm comes bundled with JSHint and JSLint. JSCS, ESLint, and Closure Linter can be installed via npm. They register as inspections and are customizable through IDE settings. They run automatically and will highlight potential issues. Pressing alt+enter on an issue will allow the user to view suggested fixes.

WebStorm has two types of autocompletion: structural completion and word expansion.

Structural autocompletion makes predictions based on its understanding of JavaScript objects, while the latter tries to predict the word currently being typed based on previously typed words. Word expansion also works in comments and docstrings and it's similar to vim's omnicompletion.

Both types of autocompletion work extremely well, have little to no problems and are quite fast even when loading suggestions on the go.

The local history feature in Webstorm tracks all your local changes in the source code that you are making. You can use it to view changes that you've made to your code and roll back whenever necessary.

WebStorm offers typescript support for building typed JavaScript applications which improves refactoring and code completion, as well as helping to find bugs.

WebStorm includes support for Meteor, Angular, and React.

WebStorm includes a feature called Live Templates. Live Templates are predefined code snippets that can include variables. They're intended to increase productivity by reducing the amount of repetitive code that has to be written.

When you install WebStorm, it allows you to choose from other IDE's for it to base it's hot keys on. So if you are switching from another IDE, it makes it a very easy transition and productivity is not adversely affected by having to learn new hot keys.

WebStorm has a powerful visual git tool, allowing for easy commits, visual diffing, merging, push/pull, rebasing, and inspecting the VCS history of a project. GitHub is supported natively - you can check out a project directly from GitHub.

WebStorm has support for Grunt and Gulp task runners.

WebStorm (and really all of the IntelliJ IDEs) support the plugins throughout their plugin ecosystem which leaves you with 100s of tools to handle your automation tasks. There is a wide range of build-related plugins that help you by having pre-defined commands to execute with the click of a button. Out of any other IDE, WebStorm has by far the most coverage when it comes to tools for your development workflow.

The theme is very easy to customize to your liking. You can change font-size, colors, highlighting colors, and more.

Webstorm supports not just Git and Mercurial, but Subversion, CVS, and Perforce as well.

This integrates with other community tools like ESLint and editorconfig.

Code Templates are powered by Apache VTL (Velocity Template Language) and allow for includes, custom variables, conditional blocks, iterators, and live templates.

Webstorm comes with icons for many filetypes which makes it easier to find what you're looking for in the project list.

WebStorm has a built-in webserver that allows you to run projects from http://localhost:63342/ProjectName.

The IDE comes with a built-in terminal, a feature lacking in some lighter editors.

WebStorm has built-in support for CoffeeScript and Dart.

Karma allows you to execute unit tests and monitor code coverage. You can read more about using Karma with WebStorm here.

WebStorm has built-in support for Sass which is one of the most stable and powerful CSS extension languages.

WebStorm has a powerful debugger, with support for conditional breakpoints.

With the settings repository, you can easily enforce your development standards.

Non-commercial open source projects, and students and teachers (including classroom licenses) may qualify for a free license. There is a 50% off license for startups (under 3 years old). You can read more about it here.

It is able to specify for example node versions, which will be used to run task for current project.

Assists with configuration and understands module resolution.

Cordova allows for building native mobile applications via HTML, CSS, and JavaScript.

Autocompletion, syntax-highlighting, refactoring, and pub integration for Dart are supported in WebStorm.

Autocompletion, syntax-highlighting.

It may seem like a complex IDE and it does have a lot of functionality, yet it uses way less RAM than barebones-looking, Electron-based IDEs.

Makes adjusting an existing or creating new themes a breeze. Especially due to things like inheritance, as well as easily exporting/distributing/importing the color settings which really only store where on deviates from the defaults (thus the resulting files are very small and relatively human-readable).

SmartGit can be used free of charge by Open Source developers, teachers and their students, or for hobby, non-paid usage. However, some features are only available with paid versions, like JIRA/GitHub Entreprise/Bitbucket integration, distributed review, DeepGit.

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.

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.

SmartGit's log viewer displays the full commit history in a clean UI. This can be filtered to only show commits matching a certain criterion (e.g. branch).

GitFlow 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.

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.

Using OAuth, you can connect SmartGit with your accounts in Github, GitLab, 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.

Compared to gitk, git gui, SourceTree, GitKraken.

This is very useful when reviewing files before committing and finding a needed quick tweak.

The built-in compare and conflict solver has syntax coloring with customizable colors.

If normal Git commands would abort because of local modifications, SmartGit can stash them and apply later after the command ran successfully, e.g. a rebase.

Apart from Git, SmartGit supports both Mercurial and SVN via a git bridge.

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.

You don't have to search all the repositories when trying out SmartGit the 1st time, but it finds all of them magically.

And support for own themes.

If screen space is limited, one can stack some views onto another. 2 layouts are available - "Main" and "Review" - with independent view positions.

Support responds quickly and they genuinely try to help you! If it's a bug, it will often be fixed within days.

Rebased, but not yet garbage-collected commits can be easily made accessible again, e.g. after a reset hard.

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.

SmartGit also has a portable bundle that can be downloaded and can be run from external devices (such as a flash drive for example) or to test-drive without leaving traces on the machine after removing.

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.

The file list view can be tweaked and filtered in many ways (e.g. regex can be used).

Can make a repo group containing multiple repos; it acts as a meta repo.

Can submit selected files from multiple repos in a repo group in one commit action; uses the same commit message in all the repo commits.

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.

Across all those years, every mistake I did I was able to recover.

Not every, but nearly all.

This allows great layouts as desired.

One payment, get updates for all future versions.

GPG in SmartGit makes for added security.

This is extremely useful in histories with a lot of merges. You can focus on the changes on the main branch and expand into a merged branch with a single click when you need to.

See here.

Supports GitBugTraq file.

Allows you to select the desired issue, instead of having to do it manually.

4GB, 10 years. Most other graphical clients either slow down to a crawl or even crash, or don't support some of the needed features.

It may look confusing at first, but once you know each part, you love how useful they are.

Git squash is a pain on CLI, and most Git clients allow some kind of squash during Rebase only. Ctrl+J shortcut helps for simple squash commits.

Or nearly everything.