7 ms·
People use it for the sake of not using JavaScript. To a React client-side developer everything should be done in React on the client-side, with maybe a sprink
by unsupp0rted 3y ago
People use it for the sake of not using JavaScript.
To a React client-side developer everything should be done in React on the client-side, with maybe a sprinkle of backend for unavoidable things, like where API keys live.
They’ll foot-gun as much backend stuff into the front end as possible.
To a certain kind of backend developer, everything should be done typesafe in non-JavaScript on the backend, with a sprinkle of client-side JavaScript for unavoidable things like showing/hiding elements. Of course even for this, 10 lines of CSS is preferable to 1 line of JS.
They’ll foot-gun as much client-side stuff into the back end as possible.
- karmarepellent 3y agoMaybe some people are using it to avoid JS at all costs. I am using it to have everything (validation, authentication) in one place, the backend. It also saves me currently four serialization and deserialization steps, which drastically improved performance. meanwhile there will also be a few 10s or 100s lines of JS to enable some specific behaviour that I do not want to (or would be awkward to) implement in HTMX. I am not saying that it is a silver bullet and people may use it for a variety of reasons, even avoid JS. I try to be less biased and make the best of both worlds. Until now, it has been pure joy.
- philipwhiuk 3y agoHappy full-stack React + Back-end guy here :)