I remember doing this with jQuery's $.ajax nearly 15 years ago. This seems comically overcomplicated in comparison. Why bother with the overhead of a websocket?
> You do not need to build an API: the server generates HTML and sends it to the client, with no middleman.
You're still building an API, it's just inside the websocket handler rather than http. Essentially this is yet another DIY RPC framework.
Why reinvent everything yet again? jQuery still exists. All the required methods still exist too. You can build a bog standard HTML website and then use progressive enhancement to fetch the next html page and replace the content of the current one with that, which has the benefit of handling middle click perfectly.
> You do not need to build an API: the server generates HTML and sends it to the client, with no middleman.
You're still building an API, it's just inside the websocket handler rather than http. Essentially this is yet another DIY RPC framework.
Why reinvent everything yet again? jQuery still exists. All the required methods still exist too. You can build a bog standard HTML website and then use progressive enhancement to fetch the next html page and replace the content of the current one with that, which has the benefit of handling middle click perfectly.