Comment by thijsvandien
5 years ago
True; that's the only subscription model I find acceptable for software that hardly changes in meaningful ways. For example, I refuse to upgrade Git Tower to version 3 as a protest against fournova's new licensing. Up to that point, I was a loyal customer and product advocate, basically buying every upgrade anyway, but by my own choice. Instead, I'll be on version 2 "forever", despite all its flaws. It was even worse for Windows users, who bought licenses (on my advice, sometimes...) for a thing that realistically speaking never came out of beta. To have a usable product to begin with, they suddenly needed to pay for a subscription. There was zero response to my email explaining this, so there's that. Now I'm keeping my eyes open for alternatives.
I also switched from Tower when they introduced subscription pricing.
My current git setup:
- Git Fork for committing, pushing
- P4 Merge for resolving conflicts (it's not a pretty app, but the fantastic feature set more than makes up for the non-native look)
- GitUp for reordering, editing and splitting commits
- Command line for the rare things the GUIs can't do
None of those cost money and I don't understand how these awesome apps are all free. I would pay for all of them, they are much better than Tower.
Emacs is free and in my opinion Magit is far, far superior to Tower / Fork / SourceTree (used them all on mac extensively at some point; out of those, fork is pretty nice and lightweight).
I'm not an emacs user but always install it (via spacemacs) everywhere solely to host Magit.
The terminal is the best and only git client you need and it will always be free. You are doing yourself a disservice as a developer by not learning how to use your terminal
I'm not sure about that in the case of git. I used the terminal UI exclusively for a long time but it's so bizarrely designed that I've been interested in using a GUI for a while. There are a lot of reasons a dev should learn to use a terminal but making git more pleasant to use isn't necessarily one of them.
GUIs aren't super flexible but they are good at taking a common flow users go through and making it stupid simple to exercise. A lot of the usage of git should be stupid simple, with only infrequent need for complex interaction. Obviously there are some people out there for which a GUI will never be sufficient for their needs, but I'd argue it isn't the common case.
I'm typically a heavy terminal user. Git is my exception. a) the UI of git cli is just so terrible that I'd rather fill my brain with more important things, and b) for viewing what's changed, `git diff` just doesn't cut it relative to a GUI.
Sourcetree is my go to git client, but if I couldn't use sourcetree I'd be OK with pretty much any git GUI. But git CLI is reserved for particularly tricky things that GUIs just can't handle well. (And I need to look up the specific flags or commands every single time.)
Cool ! Git fork looks quite like GitX (which is unfortunately not indevelopment anymore) !
I'm a big Fork advocat and use it on a daily basis, but I fear they will charge for a new version at some point in the future.
I think that because it seems they founded a company "Fork" which inevitable will need to make money eventually.
edit: I'm of course willing to pay some bucks for great software if it's a fair pricing model.
Just yesterday I noticed a "Fork Activation" option in the Fork menu with fields for an email and a license key. I think you might be right, it won't be free for much longer.
2 replies →
I found P4 Merge to be totally inscrutable, could you elaborate on what makes it so good?
It's a 3 way merge tool that works well with Fork. To be honest I can't say how it compares with other merge tools, I tried a few merge tools some time back and liked P4 best.
I suggest using SourceGear DiffMerge for resolving conflicts. Best 3-way merge conflict handling tool I've tried:
https://sourcegear.com/diffmerge/
2 replies →
I am just replying to say that I have the exact same experience. I love Git Tower and recommended it to many people, but I haven't upgraded to version 3 and likely never will - for the exact reasons that you have lined out. I think FourNova (the company behind it) is probably missing out on quite some cash here...
I'm in the same boat, and I would rather search and find an alternative when my version 2 no longer works, than to support them again.
Tower became unusably slow for me. I switched to GitKraken and have been very pleased.
Check out Sublime Merge, from the creators of Sublime Text: https://www.sublimemerge.com
I switched to Sublime Merge from using Git Tower (their licensing was awful after v3).
Never looking back, SM is amazing.
Git Tower folks: Stop pissing off your paying loyal users. Get a hint, I want my money back because you guys never made v2 properly stable and jumped on v3 for an awful cash grab. Fuck you, kindly.
Sublime HQ is an amazing company. I would pay for their products even if they charged double. Honesty and integrity matters. You’re not selling to normal sheep, programmers are a smart bunch.
There's also Fork: https://git-fork.com/
I'm really curious - why do people want a graphical git client? The command line exposes everything, and the model is simple and intuitive.
I work in a very large monorepo, so it's not like I'm working in a git tree that isn't complicated.
> the model is simple and intuitive
I nearly spat out my drink. Git is many things but those aren't the first two words that would leap into my head.
9 replies →
Say you want to find a commit that occurred around June three years ago, and look at what the repo looked like after that commit -- without checking out any files. How do you currently do it?
For me, I just Right click -> TortoiseGit -> Show Log -> scroll -> Right-click -> Browse Repository.
How long does it take you? For me it takes < 10 seconds (I just timed myself).
16 replies →
Try doing a merge with IntelliJ's 3-way merge UI. It's flippin' fantastic compared to roaming through the files and removing sections between >>>> and <<<<.
3 replies →
Many people are visual. It's a lot easier to see changes, compare diffs, and generally follow the development branches through a GUI instead of through a command line.
I think the main advantage of GUIs in general is a contextual, curated explorability that is often lacking in CLI tools. The GUI is stateful, allows the user to click on things and prod it, and hopefully shows the most frequently used features for that context. This allows even complete newbies to be productive almost immediately.
For something like git, the slightly more visual representation is a benefit to many, too.
I'm not here to knock CLIs, there are a set of tradeoffs to be made, and CLIs win in many cases (flexibility, scriptability, being able to copy snippets you frequently use, etc). The above does tend to hold true, however.
Git is famous for being unintuitive?
2 replies →
One of the advantages is you can easily explore what changes were made and merge conflicts through the tool.
I like to drag and drop commits into an order I want when doing an interactive rebase.
3 replies →
I wonder the opposite thing: why do people try to use git in a terminal?
Its output is so rich and complex that it's impossible to make it legible outside of a real GUI, with graphics and colors.
for a new person, it's almost impossible to get anything done with git command line
4 replies →
I think most folks like a graphical merge tool, such as opendiff, or at least that's what I've been able to glean.
I work on a lot of repositories, having a GUI makes it really easy to change context and getting up-to-speed quickly.
As someone else mentioned here, the graphical merge tool in IDEA is extremely powerful. Plus keyboard shortcuts to all the main Git actions. It's overall more efficient. However I always use Git IDEA + Git CLI side by side.
Switched to Fork from SourceTree, never looked back.
Thanks for your thoughts on this, Thijs! Here's Tobias, the CEO of Tower.
We want to make sure that Tower can stay a high-quality application in the long run. This means we want to constantly improve the application, add new features, fix bugs, and help users with great customer support. To be able to do that, we need a steady and reliable source of income. The thruth is: for us - a small, self-funded business - a recurring revenue model from a subscription is the only sustainable way to survive.
A model where the user gets to keep the last version after she stops paying for the product does not work for a small business. If you have a team of 1,000 employees like JetBrains, you might be be able to afford this. But not a 7-person team like ours. For two reasons:
(1) First, it doesn't provide the steady and reliable source of income that we depend on. It's the old one-time payment model of the past - which we tried and which did not pay the bills for us in the long term.
(2) Second, and maybe more importantly: very quickly, there are lots of different old versions of the product out there. People want bugfixes, documentation and support for their version, no matter if they're currently paying or if they don't anymore. With a 7-person team, we simply cannot do this. We need to focus all of our painfully limited time on _one_ version and make sure to improve that one.
Most of our users make a simple calculation: "Can Tower help me or my team save some time or prevent some mistakes?" Over the course of the next 12 (!) months, even 1 or 2 hours or a mere handful of mistakes would make this worthwhile. If so, Tower has _easily_ paid itself off.
We offer a free and fully-featured 30-day trial that will help you answer this question for yourself - without any risks or commitments.
For the customer, automatically converting long subscriptions to perpetual licenses for an old version is a major safety net (the software will not stop working if I stop paying) and it proves that the vendor is committed to improving the product enough to make upgrades compelling.
On the other hand, reasonable customers do not expect support beyond the latest version and whatever they are currently paying for: "we have fixed that in the latest version, which you should buy" is a valid and honest answer to support issues.
For a tool that can be changed with very little friction like a revision control client, the typical "calculation" about spending money is likely to be waiting for an actual troublesome situation and then get out of it with a short subscription or a 30-day trial.
To summarise, you say you're not offering perpetual licenses for old paid-for versions because you don't feel you can make clear to your customers they don't come with support.
For some reason you do expect you can sell them on this new payment model that benefits mostly you, so it's really not your communicative skills or your customers' capacity to learn that are the problem here. That really only leaves us with the financial advantage to you.
There are many comments complaining about exactly that product, you probably ought to spend a bit more time on that thread.
Try SmartGit. I don't know how it compares with Tower, but it is very powerful and easy to use. I like the way it integrates Git features into a consistent view. For example, stashes and reflog commits can be viewed and manipulated in the same log view as any other commits.
They offer both purchase and subscription models, and a free license for open source work. Runs on Mac, Windows and Linux. I've been using it for years and have always been very pleased.
Also take a look at Git Extensions. I like this product a lot. It’s open source
I switched from smartgit to fork. Fork is really nice to use and very keyboard driven. Also free.
FYI, Git Tower is made by JetBrains is made by 7 people. JetBrains is a company of 1000. Not all software scales to allow that kind of model.
Also, JetBrains can afford that model because the JDK and other software languages are changing and it's not very feasible for their users to stay on an old version for very long.
https://www.fournova.com/company
https://en.wikipedia.org/wiki/JetBrains
Same here for Adobe Creative Suite; still on version 6 (perpetual license), which I run in a Virtual Machine due to support end-of-life.
Switched to Affinity, Photo, Designer and Publisher are pretty awesome and a true replacement for Photoshop, Illustrator and InDesign. Switched 1.5 years ago, never looked back and saved a lot of money in the process. There are a few things it doesn’t have, but its impressive nonetheless. The devs are very committed to speed and anti bloat.
FWIW, I think Adobe actually adds quite a bit to Creative Cloud every year, plus they offer fonts and connections with their mobile apps and such as part of the same price. Creative Cloud today is a very different beast from CS6.
(obdisclaimer: I worked for Adobe several years ago, but have no current stake other than being on the CC photography plan)
Same boat here. I’ll concede that they do add things, but as a pretty small scale hobbyist they don’t add anything I want or need. But they expect me to pay the same full price as a pro user.
I used to buy it every couple of versions or when it went on sale, and that was good enough for my needs. No such luck anymore.
4 replies →
And I think all the plans come with cloud storage which syncs across devices.
I fought the subscription plan for LR, but realized I usually updated yearly and had this complicated file management system for my photos. For $120/year I have the latest LR versions on all my devices and only have to worry about true backup.
I do keep an eye out for a LR replacement, but I haven't found anything that comes close to LRs file management.
Intuit Quickooks is same way. Hasn’t substantively changed in 20 years but they stop you from importing new data if you don’t update to latest every 3 years. They need some real competition.
Switched to GnuCash and didn't look back. The UI is uglier, but at least it works correctly with double entry bookkeeping.
There’s Sage 50 if you want desktop, but even desktop QB is on life support and everyone’s going online.
> They need some real competition.
Have you tried Xero? I haven’t, but if you have, I’d be curious to hear your take on it.
1 reply →
I upgraded to version 3 but feel like they haven't made a product improvement since, despite the new subscription model. Staging of chunks still remains the killer feature to keep me with it but I'd be happy to switch (pay) if anything else came along.
It’s interesting to see quite a few others in here had the same struggle with upgrading to tower 3 as I had a year (or 2?) ago. Then I moved to vscode with it’s git integration and that works just as good.
I switched from SourceTree to Fork, which is awesome for me. Check it out.