3 ms·
Or possibly, you are missing something? I have a lot of experience in JS - even contributed to MooTools back in the day, until the team left to create React.
by sam_goody 4y ago
Or possibly, you are missing something?
I have a lot of experience in JS - even contributed to MooTools back in the day, until the team left to create React.
I run node on one server, Nginx with Php on another, and have plenty experience with many of the front end frameworks.
Try designing a web page - say the product page of a shoe store - multiple times. First try as though you have React (or Vue, Svelte, Angular, etc.), but never heard of HTMX, then try with HTMX as though you never heard of React, etc.
OK, its a bit of an apples to oranges comparison, especially if you would use hotwire or whatever.
Now, test those pages for responsiveness and ease of maintenance.
I did that, and the HTMX version won hands down. I was pretty surprised. You should try it; then comment again.
I now use HTMX extensively, and avoid frameworks unless they would really save time and effort.
- robertoandred 4y agoYou’re pretending that HTMX isn’t a framework. You’re also being vague on what this shoe page does. How is it handling color and size selections? Stock availability? Photo galleries? Cart status?
- pzk1 4y agoThis is good, a real objective evaluation. I think most of the critics of HTMX stems from pure front-end devs who are not really concerned of the back-end side. While HTMX is tailor made/simple, for those who needs to build full-stack, while also having the great experience of SPAs. Granted, it will never be able to compete with powerful JS frameworks on an apple-to-apple comparison, but that's not what it's designed for, It's an upgrade of HTML, not JS.