I think the other thing to worry about with live updating is client interaction security footprint. In most platforms you better be damn sure that your client rerendering code is bulletproof, because if an adversary finds an input permutation that hogs CPU or worse, panics your backend you'll really be up the creek, though Phoenix/liveview can take advantage of erlang process isolation in a way that it's way less of a concern.