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
Why should only a-tag and form-tag* be able to make HTTP requests?
Why should only click & submit events trigger them?
Why should only GET & POST methods be available?
Why should you only be able to replace the entire screen?
If this is what you need, and you have a decent backend, then doing it with htmx is far more comfortable as almost all your logic is now back where it belongs (and where you have access to sane languages): The backend.
-- a backend dev who also has to do frontend
I can’t wait for Lemmy markdown to stop being fucking broken …
So you get angled-bracket-opening letter-a angled-bracket-closing (or in other words, an HTML a-Tag), but not formatted as code? That is weird as fuck.
const foo=“”
That is meaningless, Lemmy doesn’t have issues with code, only with certain symbols.
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.
Add comment