I genuinely think htmx is the only one I have liked even after I built something substantial in it.
To me that is big, to be able to walk away from a significant amount of time with something and say "yeah! I want to use that again!" instead of some variant of "it's the least bad option" is both rare and cherished so thanks for all the hard work.
---
1: https://github.com/bigskysoftware/htmx/blob/master/src/htmx....
i often recommend it for people that want a more "batteries included" hypermedia-oriented library
https://www.youtube.com/watch?v=inRB6ull5WQ
we are talking w/the chrome developers about these ideas, i'm cautiously optimistic
I hope this does not become a chrome-only feature in that case
their latest features have started leaning into improving the hypermedia infrastructure of the web so i'm optimistic
i have told my chrome team contacts about bugs in other browsers (e.g. safari not properly updating completion results when datalist elements are replaced asynchronously) and they have communicated these issues to those teams and gotten them fixed
if anyone reading this from other browser teams is interested in getting in contact w/me they can email me at carson at bigsky dot software
You can make tabs, accordions, carousels, modals, popovers and even Pure HTML Out-Of-Order Streaming (PHOOOS) using only HTML & CSS: https://kodus.pl
we are planning on implementing a minimalist version of alex's ideas from "The Birth & Death of htmx" talk as a POC for people to look at too.
My only question: how can I get a set of those sweet sweet floppy disks?
is returning 404.
But this is weirdly hard to find on the new site as searching just opens a scoped google search.
Probably would be good to setup redirects to the new extensions site.
big congrats on the launch!
could still fold it in at some point in the 2.x line!
The entire experience using Go + Fiber (gofiber.io) + templates + HTMX (htmx.org) is fantastic. This approach has allowed us to create a beautiful modern application that's highly performant, interactive in all the places you'd expect, and simple code, deps, devops, etc.
Perhaps, there's already a good way to hijack xhr that I'm unaware of too.
Edit: Relevant link: https://logankeenan.com/posts/client-side-server-with-rust-a...
i may restructure the internals to allow for mocking out responses using events, it comes up, especially w/ extensions
Thanks for making htmx!
Thank you!
This architecture was chosen partly because I am a boomer who remembers when websites were HTML files uploaded via FTP and couldn't understand why we shouldn't just return HTML for pages that didn't need app-style functionality, partly because we wanted something easy to manage with a small number of devs (HTML+vanilla js shines here), and partly because SPAs were new-ish when we first began development and the ecosystem was very immature and a long way from coalescing around a single winner (as it has now with React).
So in this case, HTMX is used with HTML templates and ordinary routing, while VueJS is isolated to single purpose SPA-style views with their own endpoints (for example, WebRTC video). And I suspect that we will even be able to eliminate the Vue-based pages altogether with a combination of HTMX and vanilla js if we want to, with how good vanilla js has gotten.
https://bundlephobia.com/package/[email protected]
and 2.0.0 was 45.3:
https://bundlephobia.com/package/[email protected]
i think that the better web components support blew is up a little. there is a reasonable amount of fat we can cut around IE support that is still in there, planning on doing so over the next few months & slowly
17ms over emerging 4G (and hopefully cached forever after that) doesn't freak me out too much
It's not only about bandwidth, but JS code has to be parsed and executed, which takes CPU time, which is especially affecting low end mobile devices. Compare HTMX with e.g. Ajaxial, which is only 5KB minified: https://ajaxial.unmodernweb.com
One more suggestion: use `<script src="https://unpkg.com/[email protected]" defer>` in `<head>` (https://htmx.org/docs/#installing).
my understanding from the browser engineers is that javascript files are compiled and kept in a cache for the browser, and i never see compilation or execution times in htmx profiles unless someone is processing a ton of htmx attributes (1000+ row tables w/ loads of hx-* attributes per row) which is an orthogonal problem
end of the day i don't think grinding out another few K on the minified source is gonna make a big diff, although we do plan on doing things like moving to modern closures (i assume gzip nukes most of that advantage, idk)
i think a minimal preact-like htmx might be interesting, not as minimal as htmz, but something close. might be worth looking at if you are interested, the concept isn't hard and w/ different design decisions you could prob keep it really small
this isn't much of a feature upgrade, but we took the opportunity to clean up a few things and drop IE support, which will help us slim down the library over time
hopefully it's an easy upgrade for most htmx users, upgrade guide is here:
https://htmx.org/migration-guide-htmx-1/
happy to answer any questions