Stay away from Sourcetree, especially because it is, in principle, a well-made tool. You're on the right site to find those alternatives. There are enough good, free (even if proprietary) alternatives to Sourcetree that don't include an artificial dependency on the availability of a remote service, and don't force complete vendor lock-in. To the end-user, it doesn't make a difference. Atlassian claims it wasn't a marketing move, but motivated by licensing and legal considerations. This went far enough that for a while now, it's not even possible to complete installation anymore without registering for a BItbucket account and going through an online activation process.Ī requirement like this instantly disqualifies any application for me – especially if it's a free one. Over the years, Atlassian tied it increasingly tightly to their Bitbucket ecosystem. I used to like the core of the Sourcetree application, and it has even been my main Git UI for a while. Based on that experience it's likely that Atlassian's development and Quality Assurance teams were "experiencing issues" at the time, one hopes that this has now been remedied. One version had serious issues with switching between branches and, after suffering two commits being corrupted during switching, I was forced to get into the habit of backing up my work-area before doing so. Around the same time basic features were lost in a transition to a new engine with users having to wait for several updates to regain anything near the original functionality. Several times updates were issued that slowed it to a crawl (other reviews here suggest that this was around 2017) and were not fixed in an acceptable timeframe. What made me wary of returning is that it has had a chequered history. You don't know quite how helpful are little things like that until you use a package that doesn't have them. It also makes use of my preferred text editor (CRiSP) and merge tool (Beyond Compare) and I can highlight a file and instantly open it in Windows Explorer or copy its path to the clipboard. What made me decide on this rather than some of the leading free alternatives is the speed of update of the GUI when files change underneath it and the fact that the major features I wanted (such as squashing commits) are readily available and easier to use. In comparison, GitKraken's display felt crabbed and required mouse clicks or a hover to reveal what I consider to be basic information. The graphical representation of the branches in Sourcetree is uncluttered with tags and the like fully expanded. What made me decide to keep with it rather than to go with GitKraken was a small but significant matter. I've spent a little time trying other tools and I surprised myself by coming back to it as my choice of GUI. I have recently returned to Sourcetree after a couple of years using alternatives to Git.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |