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.
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.
String usage by DevOps who prefer the terminal for advanced usage or in an automated flow within a CI. Zeit.co is a great example but still early trend. Might be tough to convince your users to have this interface only.
After reading the website and looking at the current production users, it seems the project has been created by a chinese team. Some (not the majority) commits were written in mandarin. It doesn't help to bring foreign developers to contribute. Also, they might not be in touch with the influential blogs or developers on social networks to talk about their project. Many nice front end projects made by Chinese developers have the same problem.
They're easier to read and code. Check out XAML for C#, it's dead simple. But one of their main problem is they advertised for too long (I remember waiting for ages) and we didn't get the 60 fps. It wasn't as fast as announced and painful to integrate.
If you play with their JSON Template thing, you'll suffer. Honestly, that pseudo language isn't even well documented. I had to go through so many posts or questions on different forums to find all its features. Their UI tool is still a good thing but it's definitely not that developer friendly.
I'm not an iOS developer but for the native modules that I developed for Cordova or React Native, Swift is definitely a much better and cleaner language to develop it.
It's a simple yet powerful budgeting tool. YNAB always look overcomplicated and unfriendly to me