I'm using Unpoly (<a href="https://unpoly.com" rel="nofollow">https://unpoly.com</a>) instead of htmx. One thing that, sometimes, makes me consider pairing it with jQuery are the components built around it.<p>Stuff like datepickers, autocompletes and whatnot are very consolidated in jQuery world. Sure there are options for vanilla JS but they are not mantained or do not have all the features.<p>These components are being built for the Reacts and Vues frameworks these days.
You probably <i>should not</i> use jQuery unless you have an actual need for it. 10-ish years ago it was helpful because browser features were very fragmented at the time and it was hard to write code that would correctly function across all major browsers. Today, there's little difference (mostly due to them all being the same under-the-hood nowadays) so instead of being a helpful tool, it's being overused for numerous reasons. Most of what jQuery was really good at has now been added to Javascript core or there is a browser API for it.
I use it purely for the syntactic sugar. It's less characters to type than vanilla JS[0]. I've toyed with Cash[1] too which I use for small projects that don't need the entire jQuery lib.<p>[0] <a href="https://youmightnotneedjquery.com/" rel="nofollow">https://youmightnotneedjquery.com/</a><p>[1] <a href="https://kenwheeler.github.io/cash/" rel="nofollow">https://kenwheeler.github.io/cash/</a>
Mainly because so much jQuery already out there. For a fresh project it's harder to make an argument for it, but if you work with legacy code you probably have to know jQuery.<p>Personally I like jQuery. Like so many developers I started using it a long time ago because it solved numerous browser inconsistencies and incompatibilities. Then I got used to the clean and concise syntax. Now I use htmx more than jQuery.