3 ms·

How will htmx help to inclusively solve the app side of things? Given the objective, hotwire seems like the simpler, more inclusive way to solve this, but I wou

How will htmx help to inclusively solve the app side of things? Given the objective, hotwire seems like the simpler, more inclusive way to solve this, but I would be happy to see you argue otherwise.

recursivedoubts 4y ago
htmx makes sense if you have a server-side framework you are already comfortable with and that effectively addresses the problem domain at hand (e.g. if you already know django) if you are starting from zero knowledge of any server side technology and want a front-end/back-end integrated solution, rails + hotwire or laravel livewire will be better
- likortera 4y ago
  I'm working on a project with Laravel + Unpoly. It's an extremely easy and straight forward stack. And I knew zero PHP when I started, but I don't find it difficult at all.
  - jstummbillig 4y ago
    Can you draw any first hand comparison to Rails (and maybe some additional comparative tooling like Hotwire)?
    - likortera 4y ago
      I never used Rails other than doing it's tutorial, etc. And I only know hotwire by their docs, so I can't do a real life / production code comparison. But from my understanding, Unpoly manages to achieve almost the same thing that Turbo + turbo frames can do, plus some other extra goodies such as modals (now layers), forms validation, etc. I honestly like Unpoly a lot more, and it also works with any backend framework "as is", given it does not require any special behaviour from the backend. That's a big win in my opinion...learning a tool that can be used everywhere can't be a bad thing. The only thing I miss in Unpoly, is something equivalent to Stimulus. You do have "compilers" which allow you to attach custom JavaScript to any Dom element, but everything you do there is pretty manual and imperative. For these use cases I also use Alpine.
rlawson 4y ago
I have the same question! Htmx is fantastic but I really wish there was an equivalent of strada/turbo-ios in the django/htmx world. I am not an app developer so in the past have just gone the pwa/add to home screen. I guess if I absolutely had to do an app now I would do backend in django ninja and app in capacitor or react native.
- likortera 4y ago
  Try Unpoly. It's the opinionated, batteries included alternative to htmx. But still in the same spirit.
  - rlawson 4y ago
    +1 for unpoly, I like it a lot as well
mamcx 4y ago
I tried htmx first, and later hotwire because the promise of better integration on mobile sounds appealing. Htmx is super-simple to get it work. Zero setup, literally. I can't make work the simples thing on hotwire. In my mind, is like htmx=vue and hotwire=angular, ie: one is truly simple to use, integrate and is orthogonal to your current stack, the other is his own philosophy & world. Not saying hotwire is bad, just that it like is part of a setup. Htmx literally don't care about your server-side thing.

How will htmx help to inclusively solve the app side of things? Given the objective, hotwire seems like the simpler, more inclusive way to solve this, but I would be happy to see you argue otherwise.

recursivedoubts 4y ago

htmx makes sense if you have a server-side framework you are already comfortable with and that effectively addresses the problem domain at hand (e.g. if you already know django) if you are starting from zero knowledge of any server side technology and want a front-end/back-end integrated solution, rails + hotwire or laravel livewire will be better

likortera 4y ago
I'm working on a project with Laravel + Unpoly. It's an extremely easy and straight forward stack. And I knew zero PHP when I started, but I don't find it difficult at all.
- jstummbillig 4y ago
  Can you draw any first hand comparison to Rails (and maybe some additional comparative tooling like Hotwire)?
  - likortera 4y ago
    I never used Rails other than doing it's tutorial, etc. And I only know hotwire by their docs, so I can't do a real life / production code comparison. But from my understanding, Unpoly manages to achieve almost the same thing that Turbo + turbo frames can do, plus some other extra goodies such as modals (now layers), forms validation, etc. I honestly like Unpoly a lot more, and it also works with any backend framework "as is", given it does not require any special behaviour from the backend. That's a big win in my opinion...learning a tool that can be used everywhere can't be a bad thing. The only thing I miss in Unpoly, is something equivalent to Stimulus. You do have "compilers" which allow you to attach custom JavaScript to any Dom element, but everything you do there is pretty manual and imperative. For these use cases I also use Alpine.

rlawson 4y ago

I have the same question! Htmx is fantastic but I really wish there was an equivalent of strada/turbo-ios in the django/htmx world. I am not an app developer so in the past have just gone the pwa/add to home screen. I guess if I absolutely had to do an app now I would do backend in django ninja and app in capacitor or react native.

likortera 4y ago
Try Unpoly. It's the opinionated, batteries included alternative to htmx. But still in the same spirit.
- rlawson 4y ago
  +1 for unpoly, I like it a lot as well

mamcx 4y ago

I tried htmx first, and later hotwire because the promise of better integration on mobile sounds appealing. Htmx is super-simple to get it work. Zero setup, literally. I can't make work the simples thing on hotwire. In my mind, is like htmx=vue and hotwire=angular, ie: one is truly simple to use, integrate and is orthogonal to your current stack, the other is his own philosophy & world. Not saying hotwire is bad, just that it like is part of a setup. Htmx literally don't care about your server-side thing.