Carson Gross on HTMX, Hypermedia, and Contrarian Software Development

The Journey to HTMX and Hypermedia

• 🚀 Carson Gross, creator of HTMX, discusses his journey from Intercooler to HTMX, emphasizing the importance of strong opinions weakly held.
• 💡 He explains that his initial marketing approach for HTMX involved being "crazy on Twitter" by using humor and memes rather than being overly serious, which unexpectedly gained traction.
• 📚 The book "Hypermedia Systems" is highlighted as a resource for understanding hypermedia, available for free online or in hard copy.

Distilling Hypermedia and HTML's Potential

• 🧱 Hypermedia is defined as media, most commonly text like HTML, containing hypermedia controls (forms, links) that enable non-linear control flow and network interaction.
• 🌐 HTMX aims to generalize hypermedia controls, allowing any element to act as one and enabling more flexible updates within a document, moving beyond the limitations of iframes.
• ⚠️ The historical shift from hypermedia-centric web development to client-side scripting and RPC-style applications is discussed, with Google Maps cited as a turning point that popularized RPC-style interactions.

HTMX's Advantages Over RPC-Style Applications

• ⚙️ HTMX generalizes hypermedia controls by allowing any element to trigger HTTP requests on any event, supporting methods beyond GET and POST, and enabling targeted HTML replacement within the DOM.
• 📉 A key virtue of hypermedia is reducing system state complexity by eliminating the need for client-side state stores, thereby simplifying development and maintenance.
• 🧩 While offering simplicity, the trade-off is that interactivity is gated by network requests, making it less suitable for applications requiring extremely high levels of real-time, client-side interactivity.

Contrarian Views on Code Quality and Testing

• 📏 Carson advocates for longer methods and larger classes, challenging the conventional "clean code" principles of excessive decomposition and short functions.
• 🧪 He prefers end-to-end and integration tests over unit tests, arguing that unit tests often focus too much on implementation details and can become brittle.
• ⚖️ The concept of "locality of behavior" is introduced, suggesting that co-locating logic with the element it operates on simplifies understanding compared to highly separated concerns.

Vendoring, Dependencies, and the Future of HTMX

• 📦 Vendoring is favored for libraries to reduce dependencies, simplifying integration and build processes, especially in the JavaScript ecosystem.
• 🛠️ A plea is made for vendor-first dependency management systems that deliver source code rather than compiled artifacts, allowing for easier auditing and local development.
• ⏳ Carson believes in persistence and staying positive in open-source development, waiting for favorable shifts in technology trends rather than forcing adoption.
• 🌟 HTMX 2.0 was a gentle update, and while Carson acknowledges design mistakes, he prioritizes backwards compatibility over breaking changes for minor improvements.