News for hackers. Stuff that matters.
Re:Htmx vs. React: A Complete Comparison – Semaphore by throwanem on Thursday February 22, 2024 @06:21PM (#39474743)
React and HTMX aren't addressing the same problem domain. This comparison is about as meaningful as any could be under that constraint.
Re:Htmx vs. React: A Complete Comparison – Semaphore by rrr_oh_man on Thursday February 22, 2024 @06:24PM (#39474773)
Why is "dynamic web app without page reloads" not the same domain?
Re:Htmx vs. React: A Complete Comparison – Semaphore by hermiod on Thursday February 22, 2024 @06:28PM (#39474801)
That's certainly part of the domain of react applications. But there are a lot of react applications that aren't (really) in the domain of HTMX, like "local first" applications or other applications that rely heavily on browser js APIs.
Re:Htmx vs. React: A Complete Comparison – Semaphore by arandomusername on Thursday February 22, 2024 @08:23PM (#39475731)
Absolutely, but there's a huge overlap in terms of what react and htmx can serve. Most websites that use react, can just as easily use htmx.
Re:Htmx vs. React: A Complete Comparison – Semaphore by MatthiasPortzel on Thursday February 22, 2024 @06:51PM (#39475002)
It's a little like comparing HTML and JavaScript, isn't it? React is a JavaScript library (in the sense that you write your own code that calls React functions). Whereas HTMX doesn't integrate with your application logic at all. It provides a mechanism for placing your application components on the screen.