<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>htmx on Yet Another Boring Developer's Blog</title><link>https://mauricius.dev/tags/htmx/</link><description>Recent content in htmx on Yet Another Boring Developer's Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 23 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://mauricius.dev/tags/htmx/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Modern Web App without feeling the JavaScript Fatigue</title><link>https://mauricius.dev/building-a-modern-web-app-without-feeling-the-javascript-fatigue/</link><pubDate>Sat, 23 Aug 2025 00:00:00 +0000</pubDate><guid>https://mauricius.dev/building-a-modern-web-app-without-feeling-the-javascript-fatigue/</guid><description>Introduction Let’s be honest for a moment: the current state of the Front End web development ecosystem is deeply broken. I&amp;rsquo;m not the first one to say this; it&amp;rsquo;s a conversation that has been going on for at least a decade now.
The so-called JavaScript fatigue is real1. Too many frameworks, too many tools (linters, transpilers, bundlers), too many concepts (code splitting, tree shaking), and too many obscure errors (Hydration failed seriously?</description></item></channel></rss>