Kinda weird to link to the animation examples instead of the mainpage that explains what it is. And of course, HTMX uses javascript.
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
motivation
- Why should only
a-tagandform-tag* be able to make HTTP requests? - Why should only
click&submitevents trigger them? - Why should only
GET&POSTmethods 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 …
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.
Does this render fine? `` (angled-bracket-opening letter-a angled-bracket-closing, formatted as code), because I didn’t post non-working stuff.
Looks fine, but I didn’t get highlighting
const foo=""It didn’t show on webpage są code, but works in Jerboa app. If you want to render block of code use three `
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’s just two backticks with nothing between, so probably not.
That is what should be there thanks to Lemmy’s markdown issues, and why what the other person said was deeply confusing for me.
- Why should only
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.
I can see some of the benefits, especially if you’re making something very form heavy. Thank you!
fireship has a good video on it. https://youtu.be/r-GSGH2RxJs
It might be seen as an alternative/evolution/improvement of html5 maybe ?
