Can you elaborate more on what you did?
abitdodgy
jdumont
Congratulations on the launch. I’ll hold my hands up as one of the people filling your inbox 
.
I’ve actually been working on an interactive form all week, and have been trying a few client side approaches (Svelte V3, React, Vue) and some server side ones (Drab, Channels hooked up to Stimulus). When I saw LiveView this morning I immediately downed tools and had a play to see what a LV implementation would look like.
The form that was live until earlier was powered by Drab, and along with rebuilding the form half a dozen different ways I felt pretty confident putting together the LiveView version. I have to say that it excels at ease of use and logical API. Quite similar to Drab.Live in this regard and also Phoenix Channels.
That said, I ultimately put LiveView aside and finished my Stimulus/Channels enhanced form. I couldn’t quite get my head around using it with forms and changesets. LV only operating on the form, and not the inputs confused me. For example, I couldn’t work out how to dynamically add a new record to an association without having a phx-click on a button inside the form. That didn’t play nicely with the phx-validate, and it became a case of either or, and I simply couldn’t replicate what I’ve built with Channels and JS.
I suspect that I’m missing something, and will take a proper look at LiveView next week, as your comment…
…makes me believe what I’m doing should be possible.
Anyway, congratulations on the launch! Even as someone who’s very comfortable with JS, I can see myself reaching for LiveView often!
4
josevalim
Creator of Elixir
You can use Phoenix.PubSub (which Phoenix will use by default), if you don’t want to depend on Postgres. Regarding large collections, right now adding a new entry will always reload the whole page but we plan to include mechanisms were you only append/prepend items.
8
simon
Oh fantastic, thank you!
I’ll definitely take a look at this and it really is time for me to roll my sleeves up and get into Phoenix properly.
1
jdumont
Just thought I’d try out the rainbow torture test and I’m really impressed. I managed 9 windows, all cranked up to 100FPS before I hit 100% CPU usage on a $5 Digital Ocean droplet. My (high spec) MacBook Pro was having more problems with it than the remote server was.
I think you’d have to have quite a lot of users (when using LiveView as intended) before you’d put some hurt on even a modest dedicated server. Thorughly impressed!
7
Matt
brightball
wanton7
For anyone trying out LiveView, WebSocket felt really slow to connect when I used localhost:4000. It seems that there is some sort of delay at least on Windows. According to this https://stackoverflow.com/questions/15135506/websocket-connection-setup-takes-a-relatively-long-time-is-this-normal it’s caused by IPv6. So if someone is experiencing this as well, use 127.0.0.1:4000 instead.
3
pillaiindu
I asked a question about Optimistic UI 22 days ago, and had a great discussion about the possibilities of achieving it through the use of vanilla JavaScript with Phoenix and/or LiveView, but now when LiveView is released, would you guys please revisit my question and give me some insights about what do you guys think about the possibilities of achieving Optimistic UI with vanilla JavaScript and/or LiveView.
@chrismccord @josevalim @ericmj @Gazler @jeregrine @lance @scrogson @fishcakez @lexmag @whatyouhide @peerreynders @OvermindDL1 @dgmcguire
thank you!
0
zwippie
Thank you very much for your response and explaining the current state and direction of LiveView. There’s so much to explore!
It was not my intention to downplay realtime crud forms (or any other goal LiveView is pursuing). On the contrary, I don’t like building and maintaining a JS SPA, LiveView looks like it could be a game-changer.
Perhaps it’s that I see so many possibilities and get so many ideas about this that my thoughts are getting a bit unrestrained and indistinct. As you said: start small and see where things go. 
2