Visual Studio Code vs SourceTree

You can do nothing but to track changes, stage them and commit. No history, visualization, rebasing or cherry-picking – these things are left to git console or external git client.

Sometimes it doesn't tell you if you made a typo in a method name or if a method is not used and several other important features.

It's absolutely not possible to use this tool with big projects given how long it takes to search for files.

Because file search is so slow your results are limited in order to simulate a faster search.

VS Code is a general code/scripting IDE built to be lightweight and for people familiar with their language of choice, not directly comparable to Visual Studio in power or scope.

Allegedly, VS Code is "lightweight". Yet, running multiple instances of it at once, you may get many "out of memory" messages from Windows despite 16 GB RAM. (While of course also running other things. The point is the comparison with some other IDEs/editors where running them alongside the same number of other applications doesn't cause Windows to run out of memory)

Error detection and suggestions/fixes are poor compared to IntelliJ platforms

Other IDEs specific to a language often offer better tools for deep programming.

Slower than it's competitors, e.g. Sublime Text.

In WebStorm there is analyzer that checks for warnings and highlight this in yellow, here you cannot find or add it even with plugins. It is possible to have it as errors with linter but while you are actively changing file that's not very nice.

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.