I believe this is a solved problem in the sense that the tools are there. DX could be improved tho to make it more obvious tho: www.youtube.com/watch?v=AnbW...

Would love to hear your thoughts. And totally agree with Elixir happiness 😁

Thank you ❤️

I’ll try to give it a proper answer when I get some free time

Thank you 💕!! I think a higher level API for this should probably be possible 🤔

Espero q tenha se divertido tanto quanto eu 😁

So for the "Pure UI" logic, where to draw the line between using JS commands versus relying on LV assigns which might make UX suffer if connection is slow? That's the criteria I'm trying to come up with, so devs can use it to guide design decisions. What state should be tracked in the client only?

Heey thanks for engaging! Optimistic UI covers a lot of what I'm looking, but not everything. Some UI interactions have nothing to do with accessing remote data. But lots of LV developers fall in the mistake of using assigns to control some piece of UI that could be controlled by JS commands

Thanks! Didnt know this video. In my experience there’s usually a way to leverage JS cmds to drive the UI and fix UX when server feels distant. I’m trying to arrive at a definition/rule that helps identifying when this is possible. If u dont mind sharing some specific example would be very helpful 🙏

Heey Petar, in your experience how does UX gets impacted negatively? Did the JS commands help? Thanks you for sharing 🙏

Hey something like it yes, there's a bare minimal proof of concept here github.com/samaraolivei...

With those other interop tools being available, don't you think saying *no JS is a core idea* isn't very accurate?

Thanks mate! What are your thoughts on js hooks and JS.dispatch then, aren't they encouraging to write JS?

Personally I see Phoenix.JS just as a convenience layer of interoperability plus composability goodies.

Hey Josh, do you mind saying why you consider *no JS* a core idea? Asking because I don't really see it, and I'm curious to understand how exactly our experiences diverge.

Seems like #LiveView is way more popular tag

Idk how to call this approach tho?
Cross-origin LiveView?
Embedded LiveView?

The approach can also be used for a #microfrontend architecture.

Anyone exploring something like this?