I personally don’t like the htmx style of coding. It often feels like having to explain what I want to do to someone else using only a limited set of custom words, instead of just doing it myself.
I understand you but for me it’s the opposite I am not bound to using js for everything and can just return html from the server like I want. Also everything else still works I can write js if I want to. Htmx gives me more words I can use in html not less. Also I can manage the state via the url and the server. In other frameworks I often had the problem that I was writing the same logic twice in backend and frontend.
I just peeked at the docs and right off the bat I don’t like how they have conflicting attributes like hx-get and hx-post. What happens if both are set at the same time? Why not just have hx-method?
I personally don’t like the htmx style of coding. It often feels like having to explain what I want to do to someone else using only a limited set of custom words, instead of just doing it myself.
I understand you but for me it’s the opposite I am not bound to using js for everything and can just return html from the server like I want. Also everything else still works I can write js if I want to. Htmx gives me more words I can use in html not less. Also I can manage the state via the url and the server. In other frameworks I often had the problem that I was writing the same logic twice in backend and frontend.
Exactly. Not everything needs to be a goddamn SPA!
I just peeked at the docs and right off the bat I don’t like how they have conflicting attributes like hx-get and hx-post. What happens if both are set at the same time? Why not just have hx-method?