User: Password:
|
|
Subscribe / Log in / New account

Accounting systems: a rant and a quest

Accounting systems: a rant and a quest

Posted May 31, 2012 0:29 UTC (Thu) by nybble41 (subscriber, #55106)
In reply to: Accounting systems: a rant and a quest by tuxino
Parent article: Accounting systems: a rant and a quest

> hledger looks bare but its main disadvantage IMHO is its data format (formatted text files, IIUC) and the fact that it's written in haskell.

If those are the main _dis_advantages, it must be very nearly perfect. You're essentially saying that the disadvantages are that its storage is resilient and future-proof and that it's written in a language which is resistant against programming errors.

Personally, I'd list the user interface and security issues as the disadvantages, both due to its nature as an HTML-based webapp.


(Log in to post comments)

Accounting systems: a rant and a quest

Posted May 31, 2012 7:17 UTC (Thu) by tuxino (guest, #84530) [Link]

I forgot to put a simley somewhere...

Haskell is a problem _for me_ simply because I don't know it :-)
Seriously, though, I was thinking about the popularity of the language the ERP is written in and the ease of finding a developer to customize and maintain it.
This is probably a moot point, though, as the software publisher would probably be glad to receive money for this type of work :)

Text files don't seem to me like the best storage format for accounting data. RDBMS with ACID compliance where written for a reason, weren't they ? :)

Accounting systems: a rant and a quest

Posted May 31, 2012 15:09 UTC (Thu) by nybble41 (subscriber, #55106) [Link]

> Text files don't seem to me like the best storage format for accounting data. RDBMS with ACID compliance where written for a reason, weren't they ? :)

Well, I was thinking that it's a lot easier to recover data from plain text file if something happens to go wrong. However, ACID compliance is also important, particularly if there are multiple users. Perhaps an RDBMS for active storage, and plain text for backups?

Accounting systems: a rant and a quest

Posted Jun 1, 2012 12:04 UTC (Fri) by tuxino (guest, #84530) [Link]

That's what happens, in a way, when you schedule a database dump as part of a backup strategy.

Oh, and let's not forget things like foreign key constraints, stored procedures, views and other goodies, which are quite helpful when implementing accounting systems or any other similar application.

Accounting systems: a rant and a quest

Posted May 31, 2012 19:42 UTC (Thu) by mathstuf (subscriber, #69389) [Link]

The web interface is optional. It is written using Yesod as well, so any security issue that couldn't be fixed by sticking a .htaccess-obeying server in front of it would surprise me (compile time XSS security, CSRF for free, compile-checked links, etc.). There is also the command line interface (which I use with Vim for editing). It's also data-file compatible with ledger itself.

Accounting systems: a rant and a quest

Posted May 31, 2012 20:13 UTC (Thu) by nybble41 (subscriber, #55106) [Link]

> The web interface is optional.

Oh, that's good. I saw the demo on their web site and assumed that HTML was the primary/only interface.

> It's also data-file compatible with ledger itself.

And here is a good reason for using plain text files: an RDBMS storage backend would have been unlikely to interoperate with other programs. Note that it couldn't be shared, of course, but the programs would need to agree on a precise database schema where text files, given an extensible syntax, offer more flexibility.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds