Відео

Thank you!

It’s a balance between safety and performance, where two tests might contend over a shared resource like a file or a port. Safety is a good default, but in practice most tests won’t fail in this way.

Elixir docs.

The third edition of Elixir in Action is the most recent entrypoint to Elixir: www.manning.com/books/elixir-in-action-third-edition

@@toxtethogrady4610 thank you!!

I wasn’t sure when the RC would come out but I did this research and recorded a few weeks ago. I don’t cover JSON, but I think it’s fine!

I don't know of one with the same level of integration and tooling. I think Go programs tend to use CGo and Rust binaries compiled with FFI bindings (like UniFFI). I've only done CGo with C libraries, so I don't have direct experience with Rust integrations.

@@CodeAndStuff No no I mean I want to integrate a golang library that exports C libraries into elixir.

Oh, sorry for the misunderstanding! There isn't a Go equivalent to Rustler that I've seen. There have been some experiments compiling Go to wasm and running that wasm in Elixir (yasoob.me/posts/running-go-web-assembly-from-elixir/). Someone did play around with Go NIFs in 2018, but it doesn't look like it went anywhere (github.com/paulcager/gerlang). The latest thread I could find in Elixir Forum for writing NIFs in Go was from 2017, where the recommendation was to use Ports instead of NIFs (elixirforum.com/t/is-there-a-way-to-write-nifs-in-go/10638/6). These are the docs for Ports: www.erlang.org/doc/system/c_port.html

Thanks! I haven't tried phoenix_live_react yet, but if it's anything like live_svelte I imagine that it's quite different from Interita. Inertia primarily solves the problem of establishing APIs to fetch data for a page, without using LiveView / Phoenix Channels. It originally came out of the Laravel PHP community and the backend API was ported over to Elixir. On the other hand, live_svelte (and I assume phoenix_live_react) actually use the LiveView websocket to interact with the backend. This provides capabilities like pushing data updates to the client and participating in Phoenix PubSub. That's not to say you can't do PubSub in an Inertia app-you'd just have to mount the Phoenix Channel yourself. Hopefully that makes sense! If you want to know more about live_svelte, I have a video on it here: ua-cam.com/video/LBYQ_NLVKCw/v-deo.html

@ thanks for your answer. I use it inertia in a rails project and I really like it. I wonder if it makes sense to use in phoenix if there is livesvelte or live_react. It solves a different problem but anyway liveview is amazing since it basically improves the default controller view working well with SEO

I never thought I’d pay for a font, but Berkeley Mono won me over.

@ thank you so much! 🙏

We try to provide a better experience and much more possibilities over time than JS libraries

We will try to refatctor the ui and add more components to be better in terms of ui too. thank you for your support

@ thank you for authoring a very useful library that could potentially be widely adopted

@@norbertocammayo2334 ♥♥

I think it wouldn't, however the git diff should be enough to sort this out by yourself

@@QuentinDurot Got it. So the onus is on the library user to merge in upstream changes to generated components.

Hello, dear friend. I put a lot of thought into this during development. The generator shows you the diff, and as a developer, you need to manage itوthere's no other way around it. Even if there wasn't a generator and you used an independent plugin, you would always have the latest version.

However, we followed a unified approach across the entire component and will continue to improve it in the future. Each component has a property named class, which essentially serves as your custom class, so there’s no need to modify the component itself.

Thanks for the feedback and the suggestion! I'll consider it in the future. In the mean time, I have covered live_svelte which has a very interesting and productive developer experience.

Thanks for the very kind feedback, and welcome to Elixir and Phoenix!

Thanks, and welcome back to Elixir!

Htmx and LiveView JS commands are similar, but different. While they both use HTML attributes to provide frontend and backend interactions, Htmx attributes are directly written and perform API calls. On the other hand, LiveView JS commands are written in Elixir and serialized to an HTML attribute by the LiveView renderer. These commands don't perform API calls, instead relying on the websocket connection to the corresponding server process and receiving compact diffs in response.

@CodeAndStuff Thank you very much for explaining this. Appreciate your efforts. Then this is closer to SignalR

Same here. Subscribed !

I’m glad I’m not the only one! Font designers put so much work into variants all for us to just use the default and move on.

Hooks are able to push to the server through the pushEvent method: hexdocs.pm/phoenix_live_view/js-interop.html#client-server-communication

Thanks! I found out about the modal removal from core_components while researching this video. It turns out modals won't be used in UIs generated by the phx mix tasks, so this PR removed the modal when changing the generator: github.com/phoenixframework/phoenix/pull/5900

I'd highly recommend reading through the IETF draft for OAuth 2 Security Current Best Practices - it explains those more and what threat vectors exist. In decentralised landscapes like say Mastodon* and the Fediverse, there's also an initial flow known as Dynamic Client Registration, and a new internet draft I'm co-authoring called Client ID Metadata Documents, which tackle obtaining a client_id and potential client_secret without having to register with the authorization server ahead of time. *Mastodon doesn't currently implement DCR, but something similar to it.