3 ms·
I've used htmx on several projects in the last 3-4 years and it's a success story. The only issue I've had is when onboarding other developers who don't underst
by sgt 10mo ago
I've used htmx on several projects in the last 3-4 years and it's a success story. The only issue I've had is when onboarding other developers who don't understand the htmx mindset or wanting to strive for simplicity.
- recursivedoubts 10mo agodefinitely a different approach & mindset, with its own tradeoffs & feel i think we've done a decent job of getting it back into the zeitgeist though, so hopefully increasingly easy for people to at least consider nowadays
- sgt 10mo agoThanks, it's a brilliant little library. What can you tell us about version 4? I looked at the page but it's not completely clear to me.
- recursivedoubts 10mo agoThis post outlines what's going on (although it's a little out of date): https://htmx.org/essays/the-fetchening/ https://htmx.org/essays/the-fetchening/ Basically the core API will remain nearly identical, but we're moving the internals to fetch() which will allow us to support streaming responses, take advantage of the async infrastructure in JS to simplify things, etc. Hopefully most htmx users won't notice much different when they upgrade.
- cr125rider 10mo agoThanks for being a part of this community. It means a lot that you guys try to connect with users. It gives even my skeptical grey beard a tingle and a reason to try it out.