3 ms·

Is it not just the same tradeoff space we've been exploring since the beginning of UIs about how thin the UI is? It's not like putting stuff on the server side

• pier25 3y ago
  > It's not like putting stuff on the server side via livewire doesn't have strong disadvantages around latency etc. It's exactly the same latency that a request to an API will have. Obviously Livewire is not a good option for interactivity that happens exclusively in the client.
  • klysm 3y ago
    > It's exactly the same latency that a request to an API will have. Every interaction in a livewire type system requires a round trip - that's not true for SPAs. Let's say I'm developing a node based editing UI with drag and drop that lets me connect things. How on earth are you going to make that work with livewire?
    • pier25 3y ago
      Obviously Livewire wouldn't be a good fit for that (extremely rare) use case.
      • 0xblinq 3y ago
        In those cases you use alpine, and do the interactivity on the client side.
    • 0xblinq 3y ago
      > Every interaction in a livewire type system requires a round trip You’re wrong on this. You’d use Alpine and do the interactivity client side. If you don’t miss use the tool, Livewire is supposed to reach to the server in the same situations an SPA would reach to the server (updating or refreshing server state)
  • deleted 3y ago
    [deleted]