n2o

"Best" is subjective. Some might argue that Assembly is the way to go: https://asm32.info/fossil/repo/asmbb/index Personally, I had the most fun with Erlang and what happened to become N2O: https://github.com/synrc/n2o It is designed for speed not compromising reliability so it kind of looks like what you want. Python+Django probably has better ecosystem though.

N2O[0] does exactly that. You write your app in Erlang and the framework delivers the changes via websockets to the browser. You can even choose to have the changes computed in the browser through an Erlang -> Js bridge. Pretty cool. [0] https://github.com/synrc/n2o

> Erlang needs a killer framework I like N2O a lot: https://github.com/5HT/n2o

This Erlang web framework already has something like this: https://github.com/5HT/n2o Excerpt: body() -> {ok,Pid} = wf:comet(fun() -> chat_loop() end), [ #panel{id=history}, #textbox{id=message}, #button{id=send,body="Chat",postback=chat,Pid},source=[message]} ]. Also comes with bidirectional Websocket connection support. It is based on a similar project called Nitrogen.

> I'm surprised this hasn't been done, or has it and I just haven't heard about it? N2O framework might do that. https://github.com/5HT/n2o Book: https://synrc.com/apps/n2o/doc/book.pdf One pattern you can do is send events to the server, server renders data asynchronously (maintains state for each client in a lightweight process), then ships result back to client via websocket binary frames. You also decide how much rendering happens where. Can even do whole HTML elements on the server if you want.

N2O is another one. https://github.com/5HT/n2o It is really different and extreme -- in a good way. It supports both server side or client side rendering. It seems mobile performance and concurrency were the main goals in building it. But it also takes things to another level, such as it establishes a Websocket connection after it loads the page then, lets you shuffle page data as a binary (!) payload over. I've only played with it as I am not doing much web related stuff at the moment but it looks pretty cool.

Yeah, this is a common problem. From a previous post from someone else on HN, I began reading about N20, which is focused on Websockets as its first class transport. I am reading the docs because this is one of its many interesting features. https://github.com/5HT/n2o

It is handled by N2O automatically. See how https://github.com/5HT/n2o/blob/master/priv/bullet.js

This framework is really out there. It is well ... different and interesting. Here are some not so conventional things going on: * Write your page in Erlang. * Even translates Erlang to JS as a parse transform. * Websockets (with a fallback mechanism) is the default connection mechanism. * Don't want to use JSON for some crazy reason? That's alright, user Bert (and ship binary encoded Erlang terms to the browser!). * Can render stuff on the server and send the whole thing over the websocket connection. https://github.com/5HT/n2o