---
title: "💭 The Future of HTMX - YouTube"
description: "!https://www.youtube.com/watch?v=0rtpsJSLb44&t=624s"
date: 2025-01-13
published: true
tags:
  - webdev
  - thought
template: link
---


<div class="embed-card embed-card-external embed-card-provider-youtube">
  <div class="embed-card-rich">
<lite-youtube videoid="0rtpsJSLb44" title="The Future of HTMX" playlabel="Play: The Future of HTMX"></lite-youtube>
  </div>
</div>


I like the charts that Theo brings to to these videos.  Shout out for a positive k8s reference and not shitting on it.

![image](https://dropper.wayl.one/api/file/6b2d4ec0-98f2-4e58-8ab4-936b7356e7f4.webp)

Htmx brings html/css just a bit further down the complexity graph with little to no extra effort, while react allows us to go all the way full complexity at the cost of build and dev complexity to go from zero to 100 as soon as its introduced.

![image](https://dropper.wayl.one/api/file/71ac480a-4e45-4777-87eb-a9d2d8775cca.webp)

htmx brings us back to the ease of jquery ajax without any complex swapping or json parsing, all of the object parsing and html templating is done in the backend, the front end just tracks where to put it.  HTMX couples the frontend and backend much tigher, since all of the front end html is generated in the backend, done correctly it is not possible for the front end to get out of sync and try to do things that the back end does not know how to handle, vice versa.

![image](https://dropper.wayl.one/api/file/aa09051d-7e36-43a3-b6da-a6257cad1cc9.webp)

!!! note

    This post is a <a href="/thoughts/" class="wikilink" data-title="Thoughts" data-description="These are generally my thoughts on a web page or some sort of url, except a rare few don&#39;t have a link. These are dual published off of my..." data-date="2024-04-01">thought</a>. It's a short note that I make
    about someone else's content online <a href="/tags/thoughts/" class="hashtag-tag" data-tag="thoughts" data-count=2 data-reading-time=3 data-reading-time-text="3 minutes">#thoughts</a>