Proposal: Refrain from using "DeadView", endorse an alternative

[rhcarvalho]

@ErikNaslund

One of the few things I dislike about Phoenix is that I have to make the choice between LiveView and DeadView when I start creating a new page, and it’s a bit of work “switching” from a DeadView to a LiveView later on once I realize that I need it. I also need to understand and remember both the DeadView and LiveView way of doing certain things. There’s also the fact that when I’m writing helper functions I need to think about a lot more things like “am I receiving a conn or a socket here”, to be able to support both DeadView and LiveView. My ideal Phoenix incarnation would only have View, and it would be most similar to what we currently call LiveView

Could we have a LiveView that could be told to not perform the websocket connection for example? (just as a silly idea). I’m sure a lot of people have considered the plausability of this…and I’d love to read more about it!

Related thread: LiveView: Feature to "cancel" second render - #26 by rhcarvalho