you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 2 years ago (4 children)

I’m always kinda surprised when I see htmx. What’s the perks? I already have my stack, why should I change? I looked into it recently and it looked really unappealing

  • source
  • hideshow 8 child comments
  • [+] 9 points 2 years ago* (last edited 2 years ago) (1 child)
  • [–] 1 point 2 years ago (1 child)

    LOL most of your markdown rendered fine in Voyager.

    I can see some benefits, unfortunately they’re not issues I deal with in our current stack.

  • source
  • parent
  • hideshow 2 child comments
  • [+] 1 point 2 years ago* (last edited 2 years ago) (2 children)
  • [–] 4 points 2 years ago (1 child)

    It becomes pretty nice if you use a templating engine to generate html server side. Context: 95% of my work projects are java with spring boot and JavaScript applications for the front end.

    I used turbo (other js library, very simmiliar) for some prototypes and having the complete state of an application in the backend and the ability to reuse so much of my html templates allowed me to iterate pretty fast on ideas. And using htmx or turbo does not mean you can't write js ever, but you can use it for purely ui functions and leave a lot of application logic to the backend, while still avoiding full page reloads and other cool features of typical JavaScript applications.

    Big fan of the idea behind htmx, would love to actually use it for stuff that goes into production. I guess it would also be really nice for existing projects with lots of html allready written.

  • source
  • parent
  • hideshow 2 child comments