The Case Against CSS Frameworks: How We Styled 30 Production Web Apps in 14KB of Vanilla CSS
Open almost any modern web repository today, and you will find an intricate pipeline dedicated entirely to writing visual styles:
A 300MB node_modules folder running PostCSS plugins, autoprefixers, and compiler daemons.
Utility-first class strings stretching 400 characters long across a single <div> tag ( flex items-center justify-between p-4 md:p-6 lg:p-8 bg-white dark:bg-slate-900 border border-slate-200 shadow-sm hover:shadow-md transition-all... ).
Or worse: CSS-in-JS runtimes (like styled-components or Emotion) injecting <style> tags dynamically at runtime, thrashing the browser's style recalculation pipeline on every component re-render.
We have normalized the idea that writing raw, native CSS is somehow unmaintainable for production applications.
When we engineered Urban Mixo —a suite of 30 computational utilities across Personal Finance, Clinical Health, and STEM—we challenged that assumption.…