fixi

you can check out fixi if you want to see a minimalist take on it: https://github.com/bigskysoftware/fixi/blob/master/fixi.js

yeah if that's a problem you can always use fixi https://github.com/bigskysoftware/fixi

hey HN, fixi & friends are some minimalist takes on my other projects and I finally put together a small website for them. They are lower-level and rawer than htmx, hyperscript, etc, but come in at 4.5kb. fixi.js, in particular, is designed to be readable: https://github.com/bigskysoftware/fixi/blob/master/fixi.js

I mean you're not wrong: end of the day htmx is just some javascript written on top of standard vanilla javascript apis. It tries to handle things in a more html-centric, attributes-driven manner than script-oriented approaches do, but it's nothing too complicated check out fixi for our ultra-minimalist take on the idea: https://github.com/bigskysoftware/fixi Or, for extreme minimalisim, htmz, which repurposes iframes for a similar idea: https://leanrada.com/htmz/

our minimalist version of htmx is fixi.js: https://github.com/bigskysoftware/fixi 1181kb brotli'd (no minification)

> We're very close to invokers being baseline, and that will take care of plenty of what htmx was designed to do. From what I've seen, invokers without extra code are designed for client side interactivity (e.g. showing a modal), which is orthogonal to the (correct, IMO) use case of HTMX. You shouldn't use HTMX to turn every custom user interaction into a network round trip, you should use it instead of fetching JSON. If a user interaction wouldn't trigger a network request if you built your app with react/vue/svelte/{insert_framework_of_choice}, then it shouldn't trigger one if you build it with HTMX either. You can add custom commands with invokes and custom JS, but at that point you're basically re-implementing HTMX yourself, and I'm not sure what the advantage of that would be over hx-trigger="command" (especially when you also cons

there's a fair bit of functionality in htmx that isn't trivial: history support, event debouncing, etc. you can certainly write it yourself, but there are advantages to having existing functionality that is well tested and fits together reasonably fixi.js is a more minimalist take on the same idea: https://github.com/bigskysoftware/fixi agree that htmx users are weird

One other comment, if you want to experiment w/different behaviors and defaults around the general concept of htmx (generalized hypemedia controls in HTML) you can fork fixi.js which is 89 lines of code (and uses `outerHTML` as the default swap strategy): https://github.com/bigskysoftware/fixi/blob/master/fixi.js i created it as an experiment in minimalism: https://github.com/bigskysoftware/fixi#-fixijs---it-aint-muc...

See also fixi, my own take on this idea: https://github.com/bigskysoftware/fixi

maybe check out fixi, our minimalist implementation of generalized hypermedia controls? https://github.com/bigskysoftware/fixi we are hopeful that w/the work of alex petro and the triptych project that we can get some of the core ideas of htmx into the HTML spec itself: https://alexanderpetros.com/triptych/

Yes, and it actually works. I use something like htmx or fixi [1] for my frontends of side-projects. Alternatively, I could also use laravel livewire, I even argue you could use them for large-scale projects like ERP systems. I even re-build small parts of a large ERP system including the design system implemention using htmx. No need for react or similar things, if you know HTML and CSS well and are a bit disciplined. But once you don't use ORMs or have a non-monolithic architecture, you need something to validate your schema. [1] https://github.com/bigskysoftware/fixi

see also https://github.com/bigskysoftware/fixi

see fixi if you want bare-bones version of the same idea: https://github.com/bigskysoftware/fixi

maybe check out fixi.js: https://github.com/bigskysoftware/fixi