React as a Modern Polyfill: Building Simpler Frontends Without Heavy Frameworks

React as a Modern Polyfill

In the mid‑2010s, browsers lacked mature APIs, making complex UI development difficult; React filled this gap exceptionally well, acting as a sophisticated polyfill. Today, native HTML, CSS, and Web APIs have largely caught up, reducing the need for such a layer.

JavaScript Should Do Only Small Tasks

Modern native capabilities cover most use cases, so it is unnecessary to delegate all state management and DOM construction to JavaScript. Procedural JavaScript is not inherently bad; earlier criticism of jQuery‑style code stemmed from weak DOM APIs, not the approach itself. With today’s robust standard APIs, writing spaghetti code is far less likely, and for minor DOM tweaks, native procedural JavaScript remains the simplest and most efficient solution.

Thinking Levels: Drag and Drop Implementation

When implementing drag‑and‑drop (DnD) with React, developers must juggle both the virtual DOM and the real DOM, constantly wrestling with state updates, re‑render optimizations, and useEffect dependency arrays—often ending up with a lot of framework‑specific boilerplate just to move an element.

In contrast, a procedural approach using native JavaScript (or a lightweight library like SortableJS) focuses solely on manipulating the existing real DOM, eliminating the need to consider a virtual layer.

Breaking Free from the React Ecosystem

Even without React‑specific libraries, productivity can remain high. Mastery of Tailwind enables rapid UI construction without React. Modern browsers also provide powerful native elements:

Using <dialog> gives automatic focus trapping and Esc‑key closing.

Using <template> allows complex SPA‑like interactions to be built procedurally.

Complex animations can now be achieved with standard CSS.

Natural Shape of Web Application Architecture

Full‑stack frameworks like Next.js bind the front‑end and back‑end too tightly, blurring boundaries and lacking mature backend features such as authentication, ORM, background jobs, email, and file storage.

Re‑examining multi‑page applications (MPA) reveals a more natural communication model: the server returns HTML directly—the most standard and straightforward web interaction. Tools like Turbo or HTMX extend this model, allowing the server to manage state while the client merely swaps HTML fragments.

Conclusion

The belief that development is impossible without the React ecosystem is a misconception. For ordinary web applications, introducing unnecessary dual‑state management adds complexity. A combination of a mature backend framework, Turbo/HTMX, Tailwind, and a small amount of procedural JavaScript offers the least abstraction layers and the most practical solution.