4 ms·

I haven't use LiveView since the introduction of components, it'll be a good occasion to try it again. But to be honest about the "no-brainer" part, I'll proba

I haven't use LiveView since the introduction of components, it'll be a good occasion to try it again. But to be honest about the "no-brainer" part, I'll probably stick to using Phoenix for apis and websockets because I'm personally firm on not using a framework that use the (IMHO) outdated layout->view model for displaying HTML.

spiderice 5y ago
> the (IMHO) outdated layout->view model for displaying HTML What is the modern model that you do use? Phoenix is very flexible and I'm wondering if it could easily be added manually.
- conradfr 5y ago
  Template inheritance with blocks, as they do in Django or Symfony. That way you don't have layouts anymore, but (usually) a base template that an action view overloads with its own content. I know Ruby on Rails doesn't work like that so I guess that's why it didn't take in Phoenix (yet?).
  - hifly 5y ago
    perhaps you could have a glance at "surface" and see if it's what you want? I think the new .heex format also gives the basis to build what you want even if surface isn't the answer for you?
  - porker 5y ago
    Agreed. Once you're used to template inheritance it's hard to go back.