3 ms·
> Then sadly the author died, and it languished for a while until it was sold to someone else. The new owner seemed to try to keep it going, but then finally ga
by ekianjo 6y ago
> Then sadly the author died, and it languished for a while until it was sold to someone else. The new owner seemed to try to keep it going, but then finally gave up last year and crammed an absolutely awful “update” that was actually a totally different software via the automatic update process. Everyone’s financial data got locked up in this new version that is almost useless. ~20 years of financial tracking just gone. To make it worse, they did it in December, just before people would need to pull reports for tax season.
It's usually better to design your (critical) data around formats that can be shared across a multitude of applications than on the bet than a single app will forever exist. Of course, it's a trade-off between convenience and flexibility.
- tonyedgecombe 6y agoIs there an open format for bookkeeping data? I suppose you have ledger-cli but that's hardly useful for normal people.
- shawnz 6y agoThere is OFX format: https://en.m.wikipedia.org/wiki/Open_Financial_Exchange https://en.m.wikipedia.org/wiki/Open_Financial_Exchange
- chmod775 6y agoCSV file(s)? It's not like the underlying data is in any way complicated. A lot of software can export and import these. Those that can't export to CSV have usually another way of getting that data into a spreadsheet application, from where you can export it as CSV... And yes I know CSV technically sucks (varying encoding, lax standards, etc.), but it's the lowest common denominator for a lot of software.
- jmnicolas 6y agoSqLite is the solution to all our CSV problems.
- rraghur 6y agoOr as someone posted here on HN a while ago - sqlite?
- tonyedgecombe 6y agoToo far down the stack. It may be the OP's data was already in sqlite but that doesn't help even if the next application uses sqlite because the schema will be different.
- tpxl 6y agoGnu cash