WebStorm vs SourceTree

WebStorm can sometimes choke all cores of the CPU. There are numerous reports of high CPU usage.

A paid license is required to use WebStorm for commercial use. The license terms changed in November 2015 and currently require a subscription (per year: $59 personal, $129 for companies). Students can obtain a free non-commercial, educational license good for one year. There is also an option to pay on a monthly basis in addition to perks, such as a fallback commercial license that can be used for free.

This application is proprietary, and thus cannot be modified, freely distributed, or trusted for security.

To get it to run properly, you have to edit the JVM memory settings when you use Node.js. Node.js makes the small JS project you have into a "large" project that requires more memory.

Every framework or extension with any popularity whatsoever will have a plugin for VS Code. Sometimes they'll still support Atom. Only one in twenty will have native support for WebStorm.

If you want support for the latest libraries, you won't get it in WebStorm.

The Java wrapper around the filesystem doesn't actively watch for file changes (by, for example, using the fsevents api on OS X), and as a result can become easily desynchronised from the actual filesystem.

If you have an external tool acting on your project (such as a gulp task or a third-party Git client), what you see in the file browser or in open tabs becomes out-of-date. There's a feature in the context-menu for manually synchronising directories with their real filesystem equivalent, but this shouldn't be necessary and is annoying to do. You usually remember to do that anyway after you've been trying to track down a bug on a line of JavaScript that Webstorm says doesn't exist for the last two hours.

It should be noted though that this is easily remedied by going to File/Settings/System Settings and checking the "Synchronize Files on frame or editor tab activation" option. It's also recommended to more explicitly represent your workflow within WebStorm itself. Most external tools/tasks can be handled with WebStorm. And if it's not in a plug-in, then you can handle it with the File Watchers.

Webstorm doesn't use the native Windows and OSX file dialogs, which makes it more of a hassle to open projects.
For instance, you don't have access to your favorite folders on the left-hand side in their custom file dialogs.

The only way to open multiple projects is to run a new instance of WebStorm which is not ideal. WebStorm can use up to 1-1.5 GB of memory.

You need to press a combination of keys or navigate through different menu levels to carry out the two most common things a developer does. For example, to run your code, the default is Shift+F10. To go to definition, you need to click on "Navigation" first. There is no sense to this: being forced to press a combination of keys hundreds of times or navigating through different menus can be a waste of time.

Examples are an unreasonably low number of undo steps and automatic saving (which causes webpack dev server to bundle VERY frequently).

The Jetbrains team do an admirable job attempting to keep up with support for the features they wrap, but they are running an un-winnable race. For example, WebStorm 11.0.2 hangs when trying to debug NodeJS 5.0+ projects (30+ seconds before hitting breakpoint). By the time they fix it, 5.1 will be out and something else will break.

This only happens when it's not a major version.

Some operations can be slow. If you know what you want (e.g you want to touch a file, add it, commit it, and push it) you can do it much faster on the command line. However you're often not going to know what you want, so the visual diffs (for example) help massively.

Need an Atlassian account to install.

It's hard to tell when you are in a conflict state, let alone what to do if it happens.

The Windows version of SourceTree is riddled with bugs, causing some users to find it unusable.

These include failing to refresh, frequent freezing, and slow performance. The recent redesign (February 2016) has made the UI difficult to navigate.

As of 2.3.5, it needs to dial home on every start-up, else it raises alerts to compliance.

Dark Theme is now available on Windows as well as the MacOS version.

Tab looks good if you have no more than five repos. If you have a lot, you will know my pain. The source tree will not remember the order of the tab you drag. Everytime you restart the app, it will go back to whatever it likes.

Upon installation, the splash screen prompts you to login. There used to be a workaround for you to manually deploy this application in an offline environment, but they've patched it as of 2.0.20.1. It now does a dial-home on each start-up. Since it cannot reach the server, it throws an error to the user, and raises alerts to compliance.

Atlassian's final decision was that they are not going to support this feature at all. Quoted from their staff:
"We’ve never officially supported any form of pre-installation on device management capabilities. [...] As you know, last year, we removed the notion licensing and asked our developers to register the product by creating an Atlassian account. That said, SourceTree has always been a tool for the individual (emphasis mine) developer."

Choosing files of specific folders for check-in is troublesome.

UI elements have been critically broken over the last few updates--interactive rebase for example has been entirely nonfunctional for the last 3 versions--and from the JIRA tickets, it seems UI bugs are not being addressed or triaged.

With the declining stability and lack of QA for this product over the last 2-3years, SourceTree seems a risky choice for teams going forward.

There are tickets about this issue sitting there for years and marked as medium priority. I experienced this since version 1.8. Up until now, there has been no fix. If your company's policy is going to enforce you to change your password, it means you need to remove all the repos and clone them again everytime you change the password. This is the worst ever experience.

For example, the Windows version is quite slow is comparison to the Mac version.

The interactive rebase window is a pain to use, with poor UX, such as not refreshing the list once a change is made. It's a downgrade from git rebase --interactive.

Seems to not always recognize changed files, which means that they will not be pushed to remote origin either. This means if you switch branches, the files will be overwritten and you lose your progress. Very annoying.

There is a bug in 'Discard hunk' and 'Discard lines' constantly interrupting the work flow with inserting wrong line endings. Click here for more details.

When your 2FA is a hardware key, it is difficult to find a way to bring up the ability to use anything but a pre-programmed password function on the Yubikey, which doesn't add much to security all things considered what a hardware key is supposed to do.

Stops responding every 5 minutes.

Frequently unable to log in, despite the correct password.

If You decide to uninstall, you'll have to manually go to the folder inside the system and directly delete the files. If you uninstalled to reinstall fresh, this is a big issue.

You can't select the install location (anymore). This is terrible for enterprise environments. It insists to install into "Users/<Name>/AppData/Local". What? Where? Why not "Recycle Bin" or Windows Temp?

E.g. after a reset command, the graph disappears and reappears after a few moments.

Enforced registration process doesn't work, shows failure when connected to Bitbucket. Windows are too small to display installation text and options. Installs unwanted icon on the desktop. Slow and unresponsive at times.

It's so obvious that ever since 2.0, it will try refreshing each of the repo a few minutes. If you have a lot then it will drive you crazy. When you try to expand a branch node, it refreshes. Try again, OOPS, it refreshed again. Sometimes, it will take you five minutes to select the node you want.

It's possible to become overwhelmed with the information density presented in SourceTree. This is especially the case in history view, as it includes a lot of data presented in various ways.

Though this is great for getting a comprehensive overview of everything that's happening in one place, it can take some getting used to.