Fine, I'll talk about HTMX.

Shoutout Ethan for the great examples https://www.youtube.com/watch?v=cpzowDDJj24

ALL MY VIDEOS ARE POSTED EARLY ON PATREON https://www.patreon.com/t3dotgg
Everything else (Twitch, Twitter, Discord & my blog): https://t3.gg/links

S/O Ph4seOne for the awesome edit 🙏

Kevin

FaunaDB

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

htmx is a tool that allows backend engineers to build interactive UIs without having to adopt React or similar tools. It extends the server-side capabilities, making it easier to update content on the client side. It provides a natural evolution from the old Rails era and has the potential to improve collaboration between front-end and back-end engineers.

The Truth About HTMX

<p>Great pitch on HTMX. As a backend/middleware integration engineer for decades, I got sick of having to keep relearning new iterations of React recently every time the FE needed a slightly different way of accessing data that graphQL or our REST contracts couldn’t handle. I looked at SvelteKit for the backend maintenance UXes which offers a similar experience to HTMX, but it still had a learning curve. For anybody doing the old-school Flask/Jinja2, Laravel/Blade, CodeIgniter/Twig UI, HTMX is definitely the UI itch that a backend engineer needs to scratch to get a decent next-gen UX going. Simple enough that you don’t need anything else</p>
