Agree with the sentiment, the term is pretty spot on when used initially, but kinda paints “traditional” views with a kind of dark term. 
I we already have the TradWife movement, why not TradViews. 
Now on a more serious note, I think StaticViews is my favourite. Live vs Static.
There is a certain subsection of the population who may react even worse to “still” as the opposite of “live” 
If we’re making a change on the basis that it adds a bad connotation, I would suggest avoiding that pairing.
StaticView would be my vote. If not just “View” 
It seems there will be an option to use LiveViews without auto-connecting the socket. If these will replace the traditional views, deadview might not even be far off. Although deprecated would sound more neutral.
Ehn, the concept of death should not be a negative thing but that is a very different existential conversation 
Dead is the opposite of Live so it makes the most sense, but if we can’t have that then I’d say StaticView seems reasonable. It’s not really true since of course it can have JS, so you have to think of it in context (which is fine). It’s really a DisconnectedView but that doesn’t have quite the same ring to it.
Personally I’ve always found “dead view” to be hilarious so I don’t see myself not using it in every day communication, but I’m fine if the official language changes.
fwiw, I found “DeadView” kind of funny. If it’s worth renaming, simply “View” seems nice.
Yes, since the live part pertains to live updates from the server as opposed to pre-rendered. At least that’s my understanding. The default approach being view, then View would be a good alternative, (like a Live stream would contrast with stream).
I actually always assumed that LiveView and View were the names, and would conclude it was an inside joke when tutorials and guides didn’t just use View. Kinda like saying “incantation” when referring to solutions to problem-scopes, though I did side-eye it.
Deadview never bothered me but it probably does have negative connotations for some. That’s not ideal. There are situations where a regular, controller-backed view is perfectly suitable.
My suggestion would be ‘rendered view’. The view is rendered, then sent to the client. It shouldn’t be considered bad, just simple.
Thank you for posting this, totally agree! DeadView makes it sound like non-LiveViews are deprecated and should be avoided, rather than a perfectly valid approach that fits tons of uses that aren’t a match for LiveView. It fragments our already small ecosystem.
Some suggestions:
I see the main difference being that a live view keeps state in a server process, so “StatelessView”?