i think i've been open and honest about when the hypermedia approach is appropriate and when it isn't and I've been open about posting bad experiences with the library:
populist or not, i think the htmx website holds up pretty well when compared with other libraries/frameworks with respect to honestly outlining its pros and cons
Here's some hypermedia apps that I've made (caveat I use HTMF -- html-form on npm -- that is similar to HTMX but is simpler and stays closer to the native HTML):
This is like the weight tracker app but is a soccer game tracking app. The game play is much more complex then anything I've made in the other apps, I almost used a micro front end for that page, but it works fine with hypermedia. It also is a SPA as the page is always the same page using hf-select (works the same as hx-select). I'll be removing the SPA part as it is really unnecessary. I just added it originally because I didn't like the code calling the service worker code on every page. I've since made it so the service worker is under 100 bytes and then calls in the other code using importScripts.
htmx is a good choice for some types of applications:
https://htmx.org/essays/a-real-world-react-to-htmx-port/
it isn't right for everything, as I try to outline here:
https://htmx.org/essays/when-to-use-hypermedia/
i think i've been open and honest about when the hypermedia approach is appropriate and when it isn't and I've been open about posting bad experiences with the library:
https://htmx.org/essays/#on-the-other-hand
populist or not, i think the htmx website holds up pretty well when compared with other libraries/frameworks with respect to honestly outlining its pros and cons