there are not a ton -- the pain points mostly boil down to: Don't use it for extremely latency sensitive UI's (there is around trip and most of the time for mo

there are not a ton -- the pain points mostly boil down to: Don't use it for extremely latency sensitive UI's (there is around trip and most of the time for most uis this is not an issue even using a server across the world). Don't use it for animation heavy UIs (you can do animations with it but think things like game UI). It does not work offline (in most cases it s the same point with standard web and offline). All of that said, the answer to your second "question" is: There is a process (this is an erlang process and VERY light -- much lighter than a thread its not unusual to have millions of them running at a time in beam) per active page. So one per use per tab or session. Also yeah, there is no lock in -- you can have 99% of your pages use static rendering (dead pages) and just use liveview for the ones that would benefit. The choice does not come with sharp edges.