Related thread: LiveView: Feature to "cancel" second render - #26 by rhcarvalho
rhcarvalho
hubertlepicki
yeah, and if the LiveView actions supported HTTP methods, we have a full replacement for Phoenix Controllers, I think.
0
kamaroly
garrison
For the record, I actually quite like “dead view”. It’s short (one syllable, matches “live”) and the meaning is obvious (opposite of “live”). The best term tends to be the one that catches on naturally within a community (e.g. early Twitter users coining “tweet”).
It would be nice if Live/Dead views were to converge on the same patterns, though. LiveView’s provenance as a “separate” library within Phoenix has created a lot of UX issues which have slowly been cleaned up as time has gone on (1.7 was a big improvement, and heex/component functionality has been nicely unified).
Finding a way to ditch controllers and the double render would take us 99% of the way there, I think. Obviously neither of those will be easy.
7
thiagomajesk
Yeah, to me, this is the crux of the matter, not the terminology.
I think Hologram (https://hologram.page/) is going in the right direction with the concept of “pages” which feels a bit more nicely connected than Phoenix/ LiveView today. At the same time, I wonder if both maintainers had the chance to cooperate at some point instead of splitting efforts because both have pretty good ideas.
PS.: Not to completely sidetrack this discussion but I have this recurring thought about Chris sunsetting Phoenix to focus completely on LiveView as the “engine” that powers client and server live interactions. Maybe that would leave room for some innovation.
5
BartOtten
I did not forget this, just have been busy with more important things so there is a slight delay.
wispering....
Went with StaticView for the time being.
3
fotkin
felix-starman
ClassicView?
Less negative connotation at least. Still doesn’t feel quite right but better than Static or Dead if we’re wanting to avoid confusion or looking snooty
2