My understanding is (I'm on v2) is that v3 is syntax-compatible with v2 so the penalty (if there is one) for starting with V2 would be small. The areas where there are clear gaps (to my mind) are:
- web frontend - AFAICT Fava is Beancount v2 only. - importers have changed substantially - some third party systems might not yet support v3 (beancount-import comes to mind - upon which I rely heavily). Pivoting this to the positive; I'd love to hear from folks using v3 and what they use for 'favs-like' reporting / browsing and how they manage imports. I might be missing a trick here where you can switch between v2 and v3 seamlessly (for example) and still do reporting using a v2 env and select what you want from v3.? Anyone using V3 (and V2?) feel like commenting? Thanks Alan On Tuesday, February 8, 2022 at 11:33:38 AM UTC Colin Ingarfield wrote: > Hello, > > About a year ago I evaluated beancount to organize my finances. As > recommended at the time I used v2. Made some good progress but my project > fell to the wayside. > > Now I'm giving it another shot, and wondering if I should use v2 or v3? > Getting all my financial info together is a fair bit of work, and I'd > rather not change it all if v3 becomes "official" later this year. > > FWIW I'm a software developer, so if v3 requires use of git, C++ > compilers, etc., that's not an issue. But if it's unstable then I'd rather > move ahead with v2. > > Thanks for such a great tool. > > -- Colin > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/355eb4cb-0189-4679-af63-d10725289578n%40googlegroups.com.
