plainbudget

Thank you so much for the feedback — this is a very early iteration. I've been using it for several years and wanted to get it into an app. I've been getting a lot of suggestions and requests from early adopters. I will definitely take yours into consideration. There's a lot of room for improvements. Re: GUI limitation, there's a CLI which is open source and free: https://github.com/galvez/plainbudget The parser and processor have a comprehensive test suite. npm i pbudget -g I talk about the DSL design and its capabilities in detail here: https://hire.jonasgalvez.com.br/2025/may/8/plainbudget/

>That's actually my most common use. [...], I just open a new sheet I think this answer explaining your most common usage actually explains better what you've built and its (unstated) philosophy. What you've created is a "scratchpad for arithmetic" that parses the numbers in plain text.[1] (Or stated another way, a "freeform spreadsheet" without the row col gridlines.) You then choose to call that functionality "budgeting". My lightbulb moment: This is why non-existent datetime data isn't "missing" in your tool because "math scratchpads" don't need dates. I also see why you see your tool as "simpler" than the other text-based accounting tool "ledger-cli". ledger-cli is definitely not a math scratchpad; it's based on transactions of debits/credits which is overkill for a scratchpad. I understand it better now. If you want to call yo

Yeah, that's my idea with this issue: https://github.com/galvez/plainbudget/issues/4 I want to be able to have multiple "sheets" horizontally, one for each month, and then make it possible to calculate a final balance (and perhaps even a graph in the background). Nevertheless, plainbudget as a CLI tool has worked just as well for me for many years. It does take a bit of manual text wrangling in its current form, but I hope it'll grow now that it's open sourced :)

That's a planned feature: https://github.com/galvez/plainbudget/issues/6 I will work on it this week.