I understand why XMLHTTPRequest in 2025 is due to overrideMimeType, but it would seem that behind such a convenience lies the fact that the route can send you any type, and it will be overwritten instead of an error. Well, and we shouldn't forget about backward compatibility and other things either.
I respect htmx, but with all the desire to say that it will replace, it would not be entirely correct. I just see what is being replaced (XMLHTTPRequest requests without almost any customization), especially when it comes to working with a server in 2025. I understand why this is so, because that's the whole point. In a certain simplicity and functionality, but, in my opinion, there are also disadvantages to this approach.
Web developer building fast, modern websites with Nuxt. Automating workflows and backend tasks using n8n. Always exploring ways to simplify and scale projects.
Wait, we already need an alternative to HTMX? I thought HTMX was going to replace all the frontend frameworks?
you may have been the victim of a scam 🤪
I understand why XMLHTTPRequest in 2025 is due to
overrideMimeType, but it would seem that behind such a convenience lies the fact that the route can send you any type, and it will be overwritten instead of an error. Well, and we shouldn't forget about backward compatibility and other things either.I respect htmx, but with all the desire to say that it will replace, it would not be entirely correct. I just see what is being replaced (XMLHTTPRequest requests without almost any customization), especially when it comes to working with a server in 2025. I understand why this is so, because that's the whole point. In a certain simplicity and functionality, but, in my opinion, there are also disadvantages to this approach.
xkcd.com/927/
is alternative to alternative to alternative...