Видео

Looks like it's part of an effort to simplify the code generated by mix phx.gen.live. github.com/phoenixframework/phoenix/pull/5900

It just simplifies the visuals for teaching.

That's a bit of a tricky one. There's some documentation on optimistic UIs in the liveview docs (here: hexdocs.pm/phoenix_live_view/syncing-changes.html), but it doesn't directly cover the optimistic create use case. If you strictly want the exact same behavior as that tutorial-updating the UI with a page-local state-you probably should use something like Live Svelte or build a traditional SPA (but you can still use Phoenix Channels with it to make the comms go over a websocket and enable server-to-client push). Technically, this could be written as a phx hook, but I imagine it'd be more complicated than it would be worth. If your requirements are a bit more flexible, look at async assigns (docs: hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html#module-async-operations). In my experience, most of the time spent waiting for a create operation isn't a result of a slow network link. With async assigns, you can create a placeholder assignment on the socket with a loading and error state. The server can immediately push a patch to the page to show a loading indicator or optimistic item in a table, then when the processing finishes it can patch to look like a complete entry. I'm considering making a video on async assigns in the future because it's a pretty interesting solution to things like this. Let me know if you end up pursuing any of these paths!

@@CodeAndStuff Thanks so much for the reply and info. I will look into the info you have provided. I would love to see a video on the async assigns. I am wondering if there are ways to make live view sites feel as snappy as SPAs. I find navigating live view sites a bit slow compared to spa.

Thanks! I'll consider it in the future

Thanks for the idea!

I'm glad you've enjoyed the videos! It depends. I'd choose livesvelte or inertia if the project strictly requires a library that only plays well with a framework like Svelte or React, or if the team working on it has deep experience with those frameworks and timelines are tight. The best stack is the one that a team is most productive with, and tradeoffs are unavoidable. That being said, you can get a ton out of the box with LiveView JS-bailing out to hooks when / if needed. I'd definitely recommend trying out a LiveView-first approach and seeing if it meets your needs, knowing you have options.

x.com/rootcert/status/1836035549377003551

github.com/phoenixframework/phoenix/pull/5900

You caught me!

Thanks! I’d love to write Elixir at work too, but companies love their JS, Python, Ruby, etc… Some day Elixir will catch on!

Thank you! I've been having a lot of fun sharing projects with this community. Comments like these keep me motivated!

You're not alone! In fact, Postgres is coming soon: github.com/lalabuy948/PhoenixAnalytics/pull/10

I’m not sure I understand, are you wanting to reverse a blob of text character-by-character?

@@CodeAndStuff Sorry, I explained myself poorly. Imagine two lines: on the first line we have wheelright::volumeup, and on the second line we have wheelleft::volumedown. Is it possible to swap only wheelleft and wheelright to get wheelright::volumedown and wheelleft::volumeup?

Oh, that makes sense. Definitely not something supported by the extension in its current state since it considers each selection in isolation.

@@CodeAndStuff . oh thanks! any suggestions? is there any extension that does what i ask that you know of?

Looks like this one might do it: marketplace.visualstudio.com/items?itemName=SSDiver2112.SwapSelection Edit: just saw that it’s a visual studio extension, not VS Code. This would be pretty easy to build though!

Thank you!

There's a similar discussion going on right now on the Elixir subreddit: www.reddit.com/r/elixir/comments/1fcn0v0/how_do_you_manage_without_intellisense_especially/ There are always tradeoffs with any technology choice. Elixir provides trivial near-real-time messaging, the strength of the beam VM, and a very welcoming community. With the three current language server implementations in Elixir joining forces, I think we'll see great advancements in editor hints. It's possible to build great apps without leaving Elixir, but when there's a ton of frontend interactivity it may be necessary to introduce a JS UI. If type annotations are critical in an app-as they might be when there are many contributors-it's not hard to define types somewhere in a .d.ts file. It won't automatically be updated, but hopefully the type system isn't the only source of testing in the app. If you find React + RTK-Query to be productive, use it! If you need to sprinkle in some websocket interactions and want a scalable backend to support it, consider layering in Elixir or relying on a third party like Pusher. At the end of the day customers care more that you shipped, not what stack you used to ship it.

​@@CodeAndStuff I really appreciate you taking the time to respond, thank you! Funnily enough, I'm the author of that reddit thread. I decided to ask in a few places at the same time, expecting either to be ignored or receive unhelpful responses. However, I was very pleasantly surprised when the exact opposite happened. The Elixir community turned out to be incredibly welcoming and helpful. You're totally right - everyone has their own approach to development. In my case, I wanted to try something new and fell in love with Phoenix's features and philosophy. At the same time, the sudden lack of immediate feedback from IntelliSense was very jarring. Nevertheless, the plans to improve the language server give me hope. With that in mind, I've decided to stick with Phoenix and work on overcoming my reliance on type hints for now. Im looking forward to seeing how the DX evolves, and I have to admit, it seems that shipping new features in this stack will be much faster when compared to what I was used to. Thanks again for your insights <3

Haha, it’s hard to record with the AC background noise and it was like 110 degrees F outside!