It's a simple yet powerful budgeting tool. YNAB always look overcomplicated and unfriendly to me
70 karma · joined May 26, 2013
It's a simple yet powerful budgeting tool. YNAB always look overcomplicated and unfriendly to me
For the second option, you're right.
For the third one, to make it simple, it's a V8 engine inside Golang. It's not another process or server.
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.
I don't know the taste of Soylent because they don't deliver yet in UK but Huel has a small taste of vanilla and it's quite nice.
The plugin model of Nativescript is easier to write because you don't need to write the binding part but you're not showing all of the plugins already created for React Native. I'm pretty sure there are more for it than Nativescript.
I still didn't see good app written with Nativescript. The iOS demo in your links is so simple. Even with Ionic Framework, you can make better. For React Native, have a look to Gyroscope. https://blog.gyrosco.pe/the-making-of-gyroscope-running-a4ad...
I tried Nativescript and it's really good but I found myself more comfortable with React Native due to my ReactJS background. Like every hybrid solution, it depends on your knowledge, needs, targeted platforms, there is no absolute answer.