IngwiePhoenix on Nostr: So htmx is for requesty things. Having a blip in your menu bar that dynamically shows ...
So htmx is for requesty things. Having a blip in your menu bar that dynamically shows if you are or arent logged in.
And Alpinejs is for making things more interactive. You have a page with a blog post and while the Like button is a HTMX request, the comment section has markdown support and thus Alpinejs is used to render that.
I think.
I have just finished reading the htmx docs and my mind is blown. There are many, many possibilities that htmx does, that don't even require code. Like, schema validation in forms. Just return a new form with the flipping errors. xD Like, BRUH. Thats so simple, its stupid.
Wonder where DataStar fits in there, if at all. But i reeeeeally like learning this hypermedia approach - or, "no-js movement" as some blogs/articles call it. Its so cool. Like, not kidding. I just have to ensure i am not bombarding the backend _too_ much - guess this is what datastar is for, or alpine, to do some stuff on the client, but only what really needs to be there.
Aaaaaaaaa this is so cool 0.0
And Alpinejs is for making things more interactive. You have a page with a blog post and while the Like button is a HTMX request, the comment section has markdown support and thus Alpinejs is used to render that.
I think.
I have just finished reading the htmx docs and my mind is blown. There are many, many possibilities that htmx does, that don't even require code. Like, schema validation in forms. Just return a new form with the flipping errors. xD Like, BRUH. Thats so simple, its stupid.
Wonder where DataStar fits in there, if at all. But i reeeeeally like learning this hypermedia approach - or, "no-js movement" as some blogs/articles call it. Its so cool. Like, not kidding. I just have to ensure i am not bombarding the backend _too_ much - guess this is what datastar is for, or alpine, to do some stuff on the client, but only what really needs to be there.
Aaaaaaaaa this is so cool 0.0