Phoenix LiveView Info

wiki
stickies
phoenix
liveview

#52

Are we still 100% sans expected release date?

The combination of refusing us to play with the alpha and not having a release date makes me feel like when I was hopelessly in love with the hot girl in fifth grade but she wasn’t interested in me. :sob:

I’m daydreaming about this getting done so I can start working on all my queued up hobby projects!

Stuff like pushstate should come pretty quickly as a community contribution once you deem us worthy to gaze upon the holy grail of liveview @chrismccord :wink:


#53

I think it could be much easier to get to Chris’s heart :lol:

:003:


#54

Given that events need to go back to server and then return to the client to be rendered, has anyone given any thought to the upper bounds of acceptable round-trip latency between the server and browser that still has for a good user experience? Theoretically what should be the limit of acceptable latency for a plain old forms? 100ms? 500ms? Less or more?


#55

Chris has said “soon after Phoenix 1.4 comes out” (and 1.4 is due out soon!)

It has been 2 months and 2 days since it came out. Am I the only one who is so impatient? @chrismccord please let us help you, most of us accept a working prototype and are ready to work with a few bugs.

has anyone given any thought to the upper bounds of acceptable round-trip latency between the server and browser that still has for a good user experience?

I think that depends on your application. I can imagine cases in which 30 minutes are still okay, but in others you should stay below 50ms. For the plain old forms, I’m guessing around 400ms unless you are creating an app for old people (they are generally slower :stuck_out_tongue_winking_eye:). Just be sure to use the proper type=“x” on your inputs, so that the browser can do some of the work instantly.


#56

I’m sure @chrismccord is taking some time for a good reason. I’m as impatient as you (I would love to stop using JS in many use cases), but If there will be many changes to the API, people will start hating LiveView for the wrong reasons.


#57

I agree with this. I would rather @chrismccord take his time and release a solid prototype that has strong potential over something that is either broken or comes across as a toy and won’t be taken seriously. This could very well be a huge selling point for Elixir/Phoenix (hopefully not too far down the road).


#58

I am balancing LiveView and the Phoenix book right now, so bear with me :slight_smile:


#59

Thank you for the work you are doing.


#60

Hi Chris, Any updates on the progress? Eagerly awaiting LiveView!


#61

Maybe @chrismccord will suprise us in this conference https://lonestarelixir.com/2019 with an announcement of liveview???


#62

6.5 hrs to go. Not that we’re counting :wink:


#63

And? Did he? Can’t wait to play around with it.


#64

Very soon apparently :slight_smile:


LoneStar Elixir 2019 - anyone go?
#65

Some more info from @jackmarchant’s blog post :smiley:

Phoenix LiveView

Although it had already been announced (but not released yet), Phoenix LiveView was presented to the audience at Lonestar ElixirConf with a promise from Chris McCord to be released as early as the end of the month but at least in the coming months.

Chris spoke about the motivations for building LiveView and stressed the goal of delaying the inevitable single page application path for as long as possible. How long that is will be determined after release when people have had time to use it.

I am personally quite optimistic about it and although I’m happy to keep writing JavaScript on the frontend whenever I need to, it will make building prototype apps to showcase Elixir’s real-time capabilities much easier.

The conceptual programming model for LiveView is very similar to that of React and other JavaScript libraries, in that each component has a parent-child relationship, with the default behaviour that if a child component fails, it can be restarted back to its last known state. It is in this way they behave like children in a supervision tree. The similarities between frontend view libraries like React and Elixir/Erlang supervision Trees is a topic I have written about before.


LoneStar Elixir 2019 - anyone go?
#66

Also from Chris’s LoneStar talk he had just finished the implementation to run tests against LiveView, and before release wanted to implement LiveView generators and polish the documentation and guides.


LoneStar Elixir 2019 - anyone go?
#67

I hoped to see his talk on YouTube, but for some reason, it wasn‘t even recorded: https://twitter.com/lonestarelixir/status/1103408089192165398?s=21


#68

I heard the video person showed up late and Chris was almost done with his speech! That’s very bad luck for the hundreds of us who couldn’t make it to Austin but are dying to hear him discuss LiveView!!

Let’s hope the videographer for Elixirconf EU doesn’t drop the ball as the speech should be similar.


#69

If I were Chris I’d start wondering whether the videographers have it in for me. Didn’t the audio get messed up fron another keynote he did?


#70

Yeah it happened at ElixirConf 2016 in Orlando. Not sure what he did to deserve this!


split this topic #71

8 posts were split to a new topic: Phoenix LiveView is now… live!