I appreciated this bit of nuance from a post on Viget’s blog:
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
@applyin 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?”
The way you use some particular technologies can be super different from how someone else does, to the point they share little resemblance, even if they share the same core.
React is similar. Vue is similar. You can link them up right off a CDN and use them right in the browser with no build process. Or they can be at the heart of your build process, and pulled from npm. Or they can be the foundation of a framework like Next or Nuxt.
When you multiply the fact that any given single technology can be used so many different ways with how many different technologies are in use on any given project, it’s no wonder why developer’s experience on projects is so wildly different and you hear a lot of people talking past each other in debate.Tags: Article, build tool, css, css tricks, frontend, tailwind