The same library, four different libraries

Leo Bauza's post on Viget's blog draws out a distinction worth keeping in mind when front-end debates get heated. Tailwind, as Bauza frames it, comes in several flavours:

There could be a whole article written about the many flavours of Tailwind, but broadly speaking those flavours are:

1. Stock tailwind, ie. no changes to the configuration,
2. Tailwind that heavily relies on @apply in CSS files but still follows BEM or some other component organization,
3. Tailwind UI, and
4. heavily customizing Tailwind's configuration and writing custom plugins.

Leo Bauza, "How does Viget CSS?"

Stock Tailwind, an @apply-heavy setup organised around BEM or similar conventions, Tailwind UI, and a fully customised configuration with hand-written plugins share a core but little else. Two teams "using Tailwind" may have almost nothing in common.

Tailwind isn't the only example

Bootstrap follows the same pattern. A CDN link pulls in the entire built stylesheet, untouched. Downloading the Sass and JavaScript sources and wiring them into your own build buys customisation at the cost of a more complicated upgrade path. Pulling Bootstrap from a package manager references the source files through your build without editing them directly. Using the source in any form also opens the door to changing colors and fonts or trimming the parts you don't need.

React and Vue behave the same way: they can run straight from a CDN in the browser with no build step, sit at the heart of an npm-driven build process, or serve as the foundation for a framework like Next or Nuxt.

Why developers talk past each other

Multiply the number of ways a single technology can be adopted by the number of technologies on a typical project, and the range of developer experience becomes enormous. That gap explains a lot of the disagreement in public debate — people arguing from genuinely different setups while using the same words.