Adding React for routing left me maintaining two frontend stacks. I wanted declarative routes, complete HTML pages, and no required framework.
I didn't set out to build a router.
I had a project built with HTML and Web Components. It worked, and I was happy with that stack. Then a few sections needed client-side navigation.
Most pages needed to remain HTML-first for SEO and the initial render, so rewriting the entire site in React didn't make sense.
I added React only to those sections.
It solved the routing problem, but now I had React and Web Components in the same project. Maintaining both stacks became the new problem.
Four questions (MANA) for judging frontend abstractions — Minimal, Aligned, Native, Additive. Platform First, without…
How many times have you installed a massive routing framework just to parse a query parameter or...
Zero JS by default — how Astro's island architecture changes the game.
Component Architecture for React Server Components Traces the evolution from useEffect...
My journey as a Frontend & Full Stack Developer building modern web applications. As a...
Why I built it Every time I started a new React project I'd reach for a UI library and hit the same...
