Regardless of what CSS query you use to look the element up, in the jquery example you'd still have your logic (the url, etc) defined elsewhere the htmx version is symmetric with the href attribute in that it completely specifies what is going to happen directly on the element itself of course you could do something in jquery like using a data attribute to store the url and HTTP method, etc, but at that point... - Source: Hacker News / 5 months ago

An early version of Htmx was in fact based on jQuery (https://intercoolerjs.org). - Source: Hacker News / about 1 year ago

I used HTMX since the intercooler days [0] but the stuff you can make is rather limited. Also you still need the JS to deal with a11y things like expanded state (or hyperscript, apparently). If you have a lot of components to implement, everything requires thinking. I really love it for simple applications though. Resist implementing a complicated menu, live notifications, an editable data-table and such... - Source: Hacker News / over 1 year ago

To an extent, there was `jQuery.get` but it wasn't tightly integrated with HTML the original version of htmx was intercooler.js: https://intercoolerjs.org released in 2013, and that version depended on jQuery. - Source: Hacker News / over 1 year ago

:) hyperscript came after htmx htmx is version 2 of intercoolerjs: https://intercoolerjs.org which had a proto-scripting language in it, the `ic-action` attribute: https://intercoolerjs.org/attributes/ic-action I dropped that attribute (along w/ the jQuery dependency) when I created htmx, but I felt there was some merit to the idea of a lightweight scripting language that abstracted away async behavior. Once htmx... - Source: Hacker News / over 1 year ago

Dashboards, tabs, trees, ... Usually require at least some JavaScript to work properly. For some components, you may be able to use hacks around that. But I would generally not recommend that outside of experimentation. So a pure CSS framework is not going to work. It seems that you are not using a frontend framework like Vue.js. So I would recommend a library using web components for the interactivity. One good... - Source: Hacker News / 3 months ago

Can webcomponents be trivially used with HTMX? Like for example: https://shoelace.style/. - Source: Hacker News / 5 months ago

I created a simple example with a bunch of Shoelace components where they are being lazy-loaded from a CDN. I loaded the components this way to show worst-case-scenario loading performance. As you can see, it still loads quite quickly. - Source: dev.to / 6 months ago

A recent example of this was when I was helping a team get up and running with Shoelace in a Next.js application. Shoelace provides react wrappers, but they were throwing an error when Next.js tried to server-side render them. Fortunately, Shoelace ships their CEM, so I was able to use it to generate new wrappers that were SSR-safe. - Source: dev.to / 6 months ago

I've yet to see this go wrong in practice. The kinds of components that are worth publishing as web components are often large, non-trivial components. Eg media libraries, emoji pickers (like the one made by this article's author), chatbox interfaces, and so on. They are the kinds of things you only have a limited number of on your page. If a component is small and focused in scope, it's likely either written in... - Source: Hacker News / 7 months ago