Why HTMX is crushing React, Vue & Svelte.

Is your SPA framework adding unnecessary complexity? See how HTMX delivers modern interactivity by sending HTML, not JSON, over the wire.

#1about 2 minutes

Questioning the default choice of SPAs for web development

The talk begins by challenging the automatic adoption of single-page applications and introduces the context for exploring simpler alternatives like HTMX.

#2about 4 minutes

The hidden complexities of single-page applications

Modern SPA frameworks introduce significant overhead, including complex build steps, dependency management, and performance issues for content-heavy sites.

#3about 2 minutes

Revisiting the history of web development and MVC

The evolution from server-rendered pages to client-side SPAs was a long journey, but modern protocols like HTTP/2 enable a return to simpler architectures.

#4about 5 minutes

Setting up the live demo with a backend stack

The demonstration uses a backend stack of Kotlin, Spring Boot, and the JTE template engine to serve HTML directly to the client.

#5about 3 minutes

Demonstrating the core concept of HTMX

A simple button demonstrates how HTMX uses HTML attributes to trigger a server request and swap the returned content into a target element.

#6about 6 minutes

Building the shop UI with server-side templates

The e-commerce shop's product list is rendered on the server using a template engine, showing how components can be built and populated with backend data.

#7about 3 minutes