im thinking 1:1 with Laravel LiveWire which is simply based on HTTP calls
it would be nice to have with Phx out of the box
kasvith
jkdiaz
chrismccord
Creator of Phoenix
no, not something we’ll ever ship 
The whole promise of LiveView is you can add “realtime” the moment you need it, without suddenly rewriting everything and brining all this complexity. If you want good interactions with the backend, LiveView is the best choice from latency and overhead perspectives. With The LiveWire approach, you’ll have more load on the server because you’re hitting the database more frequently, doing TLS more frequently, etc. Payloads will be much larger. The only argument is memory footprint, of which the 1.0 blog outlines how a 1GB server has a theoretical max of 25k concurrent users, so even with real app workflows, many thousands of concurrent LiveView users would be no problem on small servers. As LostKonbrakai said, we have longpoll as well, with auto longpoll fallback if websockets fail, so websockets themselves also should not be a concern.
14
ovaistariq
kasvith
i-n-g-m-a-r
jc00ke
This is a great release! I was wondering if the click-to-edit of debug_heex_annotations will support opening in an editor (neovim in my case) running in a terminal? Or is that functionality OS-specific? (Maaaaaaaybe it’s not the year of Linux on the desktop… yet)
1
chrismccord
Creator of Phoenix
Anything that supports protocol urls like vscode:// can work. So if you can configure your box to take a neovim:// and pop a terminal you’d be close, tho I’m not sure how you’ll locate the active term session.
2
cgrothaus
Hej there 
!
Six weeks ago, Chris announced LiveView 1.0.0-rc.0. What are the next steps, what is the roadmap to the 1.0 release? Where are such things discussed?
Greets
Christoph
3
chrismccord
Creator of Phoenix