BartOtten
I’d like to propose that we refrain from using the term "DeadView" as the opposite of “LiveView” and instead choose an alternative. A new name could shifts our focus from a negative or lifeless impression (as “dead” might imply) to a neutral one.
After debating a while, I came up with two alternatives.
1. —— not an option
2. FrozenView
“FrozenView” also references the capturing of state at a point in time in a solid piece. The benefit of this name is that it aligns with commonly used words to describe the action to transform from a solid state to fluid state.
unfreezea view (connecting the socket)freezea view (disconnecting the socket)
Although hydration doen’t seem to be on the roadmap afaik.
The impact on the existing eco-system.
Nihil. It’s a matter of endorsing the new name and as a result documentation will be adapted over time.
- Whether your suggestion is easily implemented or inline with the state of Phoenix as it is today.
Looking forward to hearing your thoughts on this!
Best,
Bart Otten
Where Next?
Trending in Proposals: Ideas
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
rhcarvalho
Agree with the sentiment. Views, the V in MVC (most frameworks) or MTV (Django) exist for much longer than LiveView.
We needed something to contrast to the new name. It’s a similar story SPA → MPA (those were simply applications before “single-page app” became a thing).
gregvaughn
I agree overall. It was humorous the first time Chris said “DeadView” but it’s really stuck and puts a negative image on what is still very useful functionality in the right circumstances. I’ve suggested “StaticView” before but I think I like “StillView” better. Other ones that just hit me:
BartOtten
This. Every time I have to write it myself I try..well..not to.
The StaticView was also my first thought, but as we already have static_path and static_url for assets it would might cause confusion. Also it reminds me a bit of a page-as-asset (read: precompiled page on a CDN). The fact that they might include dynamic data (hello {name}) makes them less static than pages that do not.
Like those but they suffer the same as ‘Next Gen’ in being relative. In 20 years LiveView might be superseded…and is considered classic/vintage.
DeadViews is coined years ago, no need to rush alternative naming. The more thoughts the better!
hubertlepicki
How about “DeadView” and “UndeadView”?
BartOtten
Killer alternative
ragamuf
Thank you, thank you, for giving voice to something that has been quietly troubling me as well. Words convey a lot in how we communicate and welcome others and the term “dead” view is not welcoming to new members to this community who may still be very well invested in a non-liveview approach. The same is true for established members who still use these regular views that were and continue to be a valid approach to many a solution, myself included.
martosaur
Huh, I never thought of
It’s kinda too good to be replaced at this point IMO. Perhaps there are other ways to highlight dead view as a perfectly viable option? “DeadView is not Dead” post on dashbit blog or something 
DeadViewas a name with negative connotationhubertlepicki
I’m not exactly sure we have “DeadView” anymore in first place. The Phoenix Views have been replaced by co-located/embedded component rendering. There’s only LiveView, I don’t actually have any other types of views.
sbuttgereit
I actually still like “StaticView”. It’s a very boring term relative to the alternatives, but it’s probably the most immediately understandable term in contact to what LiveView does. Something like “StillView” is good, but I have to now learn what we mean by “still” to understand it… it’s not a commonly used term with understood technical meanings.
nico_amsterdam
Deadview is a misnomer for the carefully crafted HTML/JS/CSS front-end trinity, which can have lively, colorful, interactive content.
What do you think of PageByPageView ?