I see the main difference being that a live view keeps state in a server process, so “StatelessView”?
4 Likes
StatelessView, that seems technical correct and easy to grasp. To me it also makes sense as controllers are known for more stateless things: API’s.
Seems StaticView is a popular contender, but unlike StatelessView it gives me a vibe of pre-rendered, for everyone the same bits, no dynamic data (hello {name}) involved vibe.
—-
Great to see the participation in this topic! Maybe it’ll lead to somewhere, maybe it doen’t but at least we explore the ‘problem’ space together.
Throwing some others in to keep the ideas flowing:
-
ConView. Known by the use of ‘conn’ in ‘con’trollers. ‘Con’tra the continuous LiveView. But maybe a negative ‘con’notation…?
-
OneOfView: what the name suggests. Don’t like it myself but alas…
-
InstantView: An instant refers to an extremely brief period of time, often perceived as a specific point that separates two different states or events.
In everyday language, it denotes a moment that occurs immediately, without any delay. (No socket process start, no diffing, no second render, no long life…just instant) and has a very positieve connotation.
1 Like
FWIW, we don’t use the term “dead view” in the docs, nor we should. We just call them “Views” and “LiveViews”.
I am not sure additional terms are necessary, especially because LiveView ends up being the Controller + View in MVC, so it is more than a View anyway.
28 Likes
I agree we should avoid using deadview and agree with José about naming - if we really need to emphasise whether we’re talking about one or the other we could just say LiveView or a standard (or regular) view.
If José and Chris are happy with this we can edit some of the older threads to reflect this. Hopefully this will encourage use of the correct terminology moving forward too.
1 Like
I was thinking it referenced “dead render” in the docs but I was mistaken. It is in comments, though, if that matters.
1 Like
For what it’s worth, I’m philosophically opposed to rewriting history, no matter what the intentions are behind it. But it’s your site and ultimately your call.
18 Likes
I don’t think it would be an issue correcting older posts so they are in line with the proper terminology (post history would remain in tact). Though if we did do it we’d probably just stick to the titles and/or first post.
Ultimately part of the purpose of this forum is to help the community by doing things like guiding newcomers. If newbies read old threads with incorrect terminology then are more likely to use it, and this creates a burden on the mod team and our community as there will be more things to do/check/correct/explain.
Having said that I have no strong feelings either way at present, but happy to make those changes if José or Chris want us to, or we can just review things later if it becomes an issue or burden.
True, no mention in the docs. DeadView is not in any way endorsed nor official. But the term is used a few times, also by core members. recent example.
Have found discussions from years ago. Somehow the idea of renaming is popular, coming to a decision less so
-
I found a post of Chis loving
Phoenix View, which probably makes sense module name wise. However, the opposite would be ‘Phoenix LiveView’ for consistency sake, so we might be inclined to drop the prefix: View vs LiveView. -
Simply
Viewis quite hard to distinguish in spoken words, not great seo/findability wise and one may be inclined to ask “What kind of view? LiveView or [one of the currently floating options]View?”. The lack of contrast to LiveView is the reason ‘DeadView’ came to use. Human nature called. Pre? View is named in MVC. -
The community seems to favor
StaticViewup to this point. It emphasizes that the page is rendered once and does not change dynamically. -
The stateless nature of the view is also mentioned a few times at this forum, making StatelessView a natural -but for newcomers less known- fit.
-
[new!]PureView– pure is well known in the context of functional programming, where functions yield the same output given the same input without side effects from stored state. Also it can be seen as ‘not bundled with controller like LV’, just the view.
I’m fine with all of them, just want the community to name it consistently and without negative connotation.
2 Likes
I actually really like PureView, but since we’re worried about connotations here, I could see that giving people the impression that they are better than LiveViews. What’s better Living than Living Pure?
1 Like
More candidates:
- Oneview, Onceview, Monoview, Uniview, to emphasis it is rendered once
- Firstview (first render), Lastview (not changing), Freeview (no socket attahed), Dumbview (not needing javascript)
It’s going to be a lot easier to change anyone who isn’t comfortable with the concept of death’s view of life and death than it is getting a forum full of developers to agree on a name 
.
If the balance needs to be corrected, call it a LoveView.
2 Likes
For me, LiveView is all about a seamlessly updated state, in which the content on the page is never stale… so what if the opposite was called a StaleView? It’s 2 syllables like LiveView, stays away from the whole death thing, and is more focused on the state of the rendered output?
1 Like
Stale implies something is not good for consumption anymore.
DisconnectedView is what I call it at both my restaurants
1 Like
No need to agree. The way I envision it is this topic being a consultation, which will lead to a proposal, the proposal itself can be presented to the community just as a last check if there is no oversight cq. reason to ‘forbid’ it.
It doen’t need to be an official name, just a guideline followed by the majority (I hope)
After all: deadview is widely used
- without any official status
- without all people liking it
- without being perfect
- without ever reaching consensus
Would be nice if key figures in the community can endorse it, simply to speed up adaptation, but
that’s a nice to have.
1 Like
True. I personally tend to StaticView at the moment. Isn’t perfect but seems to be neutral, natural and is not untrue.
1 Like
The 2 syllables is nice. However, ‘stale’ is usually not a good thing afaik. Data going stale (outdated), products going stale (don’t eat those).
Who can beat StaticView with a 2 syllables variant?
‘Dumb’ is not considered very positive. Maybe BareView instead?
Now I think of it: better find a brainstorming tool. Hoping to find a “Yes, this is IT!” variant by iterating (even posting variants I deem not to be viable); a tool could make it more visual and would allow us to ‘thumb up, thumb down’
So I asked ChatGPT:
1 syllable word which represents static, non-continuous or stale without negative connotation.
A good candidate is still.
“Still” is a one‐syllable word that conveys a state of being unchanging or motionless—essentially static or non‐continuous—without carrying any inherently negative connotations. For example, a “still image” is simply a non-moving picture rather than something undesirable.
Now I think of it: the reason I removed the option was due to a thin link with “death”. But…that connotation is only there due to the current naming. Do you agree @zachdaniel ?
I must admit the 3 syllables ‘StaticView’ does feel like a 2 syllables for me. Very different than ‘Stateless’. Am I the only one or is it common due to the ‘ic’ being almost silent when followed by View?
To me the suggestions have the issue in that they ignore that the view could be made dynamic through other means. For example, the StaticView could be rendering a dynamic app via React or Ajax, so there is nothing static about it. That’s why I am ultimately happy with just calling it View or, informally, a regular View or if you want to be precise, a non-live View (it doesn’t mean it is dead, it is just that it is not a LiveView). I think adding a new word, at this point in time, will probably just cause more confusion. My two cents.
22 Likes
