The main problem with solutions like these I see, is that if something else also want to use the same backend it becomes very hard.
In my opinion it makes a lot of sense to realy on protocols like Rest or GraphQL so you can easily use the frontend or the backend. For example you could move the backend to AWS async, or you can build some widget with Rust. You can't do those things if you tightly couple your backend to your frontend. But for some apps that might not be a problem.
The main problem with solutions like these I see, is that if something else also want to use the same backend it becomes very hard.
In my opinion it makes a lot of sense to realy on protocols like Rest or GraphQL so you can easily use the frontend or the backend. For example you could move the backend to AWS async, or you can build some widget with Rust. You can't do those things if you tightly couple your backend to your frontend. But for some apps that might not be a problem.
Please see my answer here.
Having actual json for the queries is pretty nice. But it does seem rather niche. Same for similar solutions like fulcro.