Exercise 1: Why Tailwind Can't Ship One Precompiled Stylesheet — Possible Solution
====================================================================

WHY A COMPLETE, PRECOMPILED STYLESHEET ISN'T PRACTICAL
------------------------------
Per this chapter, "cssfw1-3's own design system can generate an
enormous number of possible utility class combinations — every
spacing value, every color, every variant, every breakpoint,
multiplied together. If Tailwind shipped one complete, precompiled
stylesheet containing every possible class it could ever generate,
that file would be enormous — genuinely impractical to ship to every
user." Tailwind's own configurable design system (spacing scale,
color palette, responsive breakpoints, state variants, and their
combinations) produces a genuinely huge number of theoretically
possible class names when multiplied together — far more than any
single real project would ever actually use. Precompiling and shipping
CSS for every one of those theoretically possible combinations, for
every user, regardless of which classes a given project actually
uses, would mean downloading a massive amount of entirely unused CSS
on every page load.

WHAT CONTENT SCANNING DOES INSTEAD
------------------------------
Per this chapter, "Tailwind's own build process scans a project's
actual source files... looking for class-name strings that appear
anywhere in that source code, and generates CSS only for the classes
it actually finds — it never generates a giant, complete stylesheet at
all." Rather than starting from "everything possible" and shipping all
of it, Tailwind's build process examines the actual HTML/JSX/template
files a specific project contains, identifies which class names are
genuinely present in that project's own source code, and generates a
final stylesheet containing ONLY the CSS rules for those specific,
actually-used classes — resulting in a final stylesheet sized to match
what a given project genuinely needs, rather than the theoretical
maximum Tailwind's own design system could produce.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains precisely why the theoretical combinatorial size of
Tailwind's own possible utility classes makes a precompiled,
ship-everything approach impractical, and explains what content
scanning does instead, using the chapter's own wording for both parts.