Asayer's platform is  dedicated to providing insights and resources for developers and DevOps teams, focusing on web application monitoring, session replay, and error tracking. Through articles, tutorials, and case studies, Asayer offers insights into visualizing user sessions, reproducing bugs, and optimizing user experiences. Developers and QA engineers can learn about monitoring user interactions, detecting UI/UX issues, and improving web application performance and reliability.

asayer

HTMX 2.0, released in June 2024, brings several significant improvements to the JavaScript library used for creating dynamic web applications directly in HTML. New features include better support for Web Components, adherence to HTTP standards, and improved extension management. The new version addresses limitations and non-standard behaviors of HTMX 1.0, and migration to HTMX 2.0 requires minimal effort due to the focus on backward compatibility. A public roadmap is being developed, and more details can be found through the HTMX community and GitHub page.

HTMX 2.0 is here: Everything you must know about it

From HTMX 1.0 to HTMX 2.0: Migration Guide

Found a typo under the “New swap() API” section
<blockquote>
This function was not part of the public HTMX 1.0 JavaScritp API and was only used internally.
</blockquote>

When I started to used, it I loved it. I said yes! this makes everything simpler. but after I figured out this <a href="https://htmx.org/essays/htmx-sucks/" target="_blank" rel="noopener nofollow">https://htmx.org/essays/htmx-sucks/</a>
So if the creator doesn’t take serious his creation and says that htmx sucks, why to use htmx?

Going to the server for every single ui update doesn’t look like something effective. It may be good for desktop apps like Tauri-based apps - when backend is very close to ui part. But for browser web apps I think it may be laggy.

Can someone convince me why this is worth using and isn’t “just another javascript way of writing html” ?