I use bean-report for a few commands, mainly to get the price database, and all balances. For most operations I use bean-query or the web interface, which is fast and reliable.
I don't use Fava and I feel it adds too much complexity. It depends on a lot of external code that I don't have time to review (I just tried to count it: npm wants to install 588 packages of JavaScript code!). Running it inside a sandbox (Docker) is possible but it's harder to set up and this infrastructure can have other problems. Fava doesn't have the simplicity that I find in beancount. It also didn't work without JS when I tried it some years ago (maybe it has improved). I'd be fine with uglier web pages if they provide the basic accounting needs. Though they don't need to be ugly. I also use the holdings code and aggregate_holdings_by, but I could do the same in some other way or keep the old code. On Sun, Apr 1, 2018 at 8:53 AM, Martin Blais <bl...@furius.ca> wrote: > How many people here use bean-report as their main way to generate data > from Beancount? > How many use bean-web? > Does anybody still care about bean-web now that Fava exists? > > Also... is it possible to bean-bake Fava (or some equivalent creation of a > static version for sharing)? > > Any input appreciated, > > > (Reason I'm asking is: I'm thinking about > - rewriting the query engine to something more powerful and general, and > promoting it from experimental and somewhat flaky to the main way of > getting data out > - rewriting bean-web to be a dumber, more generic web interface that > basically renders SQL queries (using the new query engine) without any > special treatment (just tables and tree-tables) > - deleting bean-reports and all of beancount/reports, or replacing most of > it by SQL queries > - in the process deleting the Holdings code > Basically, I think that with a slightly improved query engine I could > delete a ton of code without removing functionality at all.) > > -- > You received this message because you are subscribed to the Google Groups > "Beancount" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beancount+unsubscr...@googlegroups.com. > To post to this group, send email to beancount@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beancount/CAK21%2BhPZh%2BRSFNoSDZd3PF%3Dh0ki2Utqv% > 3Dx%2BC%3D6dQpSiwX7S_ew%40mail.gmail.com > <https://groups.google.com/d/msgid/beancount/CAK21%2BhPZh%2BRSFNoSDZd3PF%3Dh0ki2Utqv%3Dx%2BC%3D6dQpSiwX7S_ew%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To post to this group, send email to beancount@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAJKAhPD9qna%2BHq73uXsuw%3DNMqE4%3DdroVpm9cvGd1Fqch0eBhMg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
