5 ms·
The final straw for me was in 2019. My 3 year old version of QuickBooks Pro refused to import any more bank transactions until I upgraded to a newer version.
by kerneloftruth 5y ago
The final straw for me was in 2019. My 3 year old version of QuickBooks Pro refused to import any more bank transactions until I upgraded to a newer version. Nothing had changed with data formats or anything -- it was simple extortion: upgrade or the software you own will cease working (fully).
Fuck them. I just wrote my own. I first tried some alternatives like GNUcash, but found it best to just write what I needed (account ledgers, reconcile bank statements, generate P&L and BS reports). I refused any other solution with any dependencies on "the cloud" or any entity.
QB is truly about the shittiest software on the planet, a reputation maintained and expanded over the decades. The simplest recourse, with minimal emotional toll, is to just not use their crap.
- dottrap 5y agoI was in the same boat. QB refused to import for a year or two, and then after than completely ceased working unless I upgraded. I stopped using it. I didn't like GNUCash. I found a small indie commercial piece of software which was more like the old Quicken than Quickbooks, but it was good enough for my purposes. But I've been worried if that indie is going to survive financially. Any tips on writing your own?
- kerneloftruth 5y agoI wanted to like GNUCash, but I just didn't. I had the same concerns re: other apps. I used the situation as a reason to play with developing a standalone app using Go, with sqlite3 as the database (basically a localhost web app). It was actually a fun side project, with the satisfaction of being free from Intuit. With it being go and embedded sqlite3, there are basically no dependencies to worry about.
- MeinBlutIstBlau 5y ago