Nitrogen for Erlang (http://nitrogenproject.com/ http://nitrogenproject.com/) does much of this. N2O, also mentioned in another post, is a variant of the Nitrog

Nitrogen for Erlang (http://nitrogenproject.com/ http://nitrogenproject.com/) does much of this. N2O, also mentioned in another post, is a variant of the Nitrogen approach. Basically, you build your application frontend with pure Erlang terms to construct server-side templates, then make live changes to the interface over and websockets (as of the soon-to-be-released v2.3), ajax, or comet (if websockets are not available, or the websocket connection crashes, it'll establish reconnection or fallback to comet/ajax). I recently did a talk at the Chicago Erlang Conference about it: https://www.youtube.com/watch?v=nlV4gm8SpVA https://www.youtube.com/watch?v=nlV4gm8SpVA