honest comparison

css-is-awesome vs Tailwind vs Bootstrap

Three good tools. Different jobs. Here is where each one actually wins — and where cia is the only one that does the thing.

Feature	css-is-awesome	Tailwind	Bootstrap
Installation	1 <link> tag	Build step required	1 <link> tag
Gzipped core size	~2 KB	~10 KB (utilities JIT)	~25 KB
Full bundle gzipped	~10 KB	varies (JIT)	~29 KB CSS + 25 KB JS
Mixin APITailwind rejects mixins on philosophy	Yes	No	Yes
Utility classesAll three ship utility class sets	Yes	Yes	Yes
Runtime theming (swap one file)Only cia lets you swap the entire visual identity by replacing one CSS file at runtime	Yes	No	No
Theme files shipped	6	0 (config only)	2 (light / dark)
Requires a build step	No	Yes	No
JavaScript dependencyBootstrap's dropdowns, modals, tabs need bootstrap.js	No	No	Yes
Readable class names in your HTMLcia and Bootstrap use semantic BEM-style; Tailwind stacks utilities	Yes	debatable	Yes
Tree-shakeable	opt-in core/utils bundles	Yes	sort of
Component count	~12 atoms + ~8 molecules	0 (utility-only)	~30
Years of battle-testing	new	5+	12+
GitHub stars	handful	80k+	170k+

Where each one wins

You want prebuilt components with a decade of battle-testing, and you don't mind the weight.

You want maximum control via utility classes, you're fine with a build step, and a huge ecosystem matters.

You want a tiny, honest SCSS system with a mixin API, and you want to reskin your site by swapping one CSS file.

The differentiator