3 ms·
Yes, no doubt there are many applications for which htmx (or any other tool you can name) are not ideal. For me, I’ve found it useful and easy to add ajax-type
by leephillips 4y ago
Yes, no doubt there are many applications for which htmx (or any other tool you can name) are not ideal.
For me, I’ve found it useful and easy to add ajax-type progressive enhancements to old-fashioned Django sites, for example. And they work just as before for users without javascript.
- PaulHoule 4y agoThat's what I am doing. I find the "standard model" of writing your application twice these days (write a back end and write a front end) is highly expensive particularly for applications that require agility. I worked at a place where we built a system people would complete tasks (like AMZN's Mechanical Turk) to train machine learning models and it should be quick to just push a new task out to people by writing a new a file, but with the single-page-application you need to not just write the back end but also recompile the front end and force people to reload it. Contrast that to an "old-school" application where you put up a new file and your new task is online. I found HTMX is great for my own model trainer/workflow system. I still can't understand why all the web design shops in my town that were doing great with Ruby on Rails felt compelled to do everything in Angular (which they struggled at) and then ditched angular for React (which they've stuck with.)