Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

HTMX is not perfect and there are many situations when you probably don't want to use it, but I think it should be considered the default answer to the question: What framework should I learn to build a dynamic frontend?

At the moment the answer to that question is "react" and while react can be cool (I've heard) it has developed into a complex world that requires quite some time to master. Even intuitive JS frameworks like Svelte have been getting a lot bigger in order to be more feature complete.

HTMX is the Pareto answer to building dynamic frontends. It will be great for 80% of all projects that require interactivity while doing that job in 20% of the complexity that react would bring.



Is HTMX a legit solution for single-page applications? Feels like you just move the complexity to the server side. For example, the server side code for a simple TODO app is a massive programming project as seen in this repository:

https://github.com/guilycst/go-htmx-todo-list/blob/main/inte...


I consider moving the complexity to server to be a net win. Never trust the client to do the right thing.

More importantly, quite often the complexity is duplicated for both front end and back end.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: