Jen here- founder of Lunch Money. Definitely give us a try if you're looking for something more modern and user-friendly. Lunch Money is less rigid than YNAB so much easier to get started on and build habits with.
If you (or anyone else reading this) decide to try it out, let me know you're from HN and I'll hook you up with a free month on top of the 14 day trial :)
We don't adhere to any one budgeting philosophy. While we won't walk you through the envelope style budgeting the way YNAB does, you can certainly mimic it with the platform!
* OXF import so that duplicate transactions are not an issue.
* An iPhone app so my wife can see the state of the budget.
* Envelop budgeting by default.
Lunch Money meets none of these. I don't think I am the target market, but the UI has won me over. I'm totally going to do everything I can to make this work. I suspect the API will make that possible.
Amazing job on the interface, clean fast and appealing while showing loads of information all at once.
Serverless took over that niche. First with AWS Lambda & Google Cloud functions and nowadays solutions, like Google Cloud Run, do the same thing as Dokku & co without having to care about the ops part. They still make sense for the ones who use cloud providers with less offerings like Digital Ocean and don't want to deal with Kubernetes
1996 you're wrong on "West hates Huawei so much". American might not have a great opinion of the brand but VLC is French project and I can tell you Huawei is popular in France. USA doesn't represent the whole West, just part of it.
My friends from the mainland call these people “愤青”, basically young extremely patriotic men.
Basically any sleight against China and they’ll come in droves, screeching people down and proclaiming the eternal glory of the lunar kingdom (and its subsidiaries).
Fortunately, as this thread shows, English language forums only get one or two of these crazies at a time.
For example, in terms of latency because of the network round-trips to establish the connection (or even just to send an additional HTTP request inside the existing session and wait for a reply!).
The first one is to use NodeJS as your front end server and Golang for your API.
The second one is to use NodeJS with React as an internal micro service to returns the HTML content back to the Golang front end server.
The last one is to use a JavaScript interpreter within Golang. Some developers are doing the same in Java. Check this project for this option: https://github.com/robertkrimen/otto
Now the question is which one is good. As always it depends on what you're looking for. I would say the NodeJS micro service renderer would be my favorite as it keeps all the complex logic in Golang.
Could you explain NodeJS + Golang API (option 1)? How should Golang handle the API if I'm using a NodeJS/Express server as well?
Golang + NodeJS microservice (option 2) is the same as the example I gave right? Where the client only communicates with a Golang server, which forwards the request to NodeJS/React for processing. The processed response is then returned by the Golang server.
Golang + JS interpreter (option 3), again the client exclusively communicates with a Golang server. But Golang types are translated to the equivalent React JS components. Then processed with NodeJS/React and returned as a response by the Golang server. Is that all right?
It's a simple yet powerful budgeting tool. YNAB always look overcomplicated and unfriendly to me