'Disambiguating Tailwind'

A passage from Viget's blog post impressed me:

There are many uses of Tailwind, and you can write a whole article, but in general, these usages include:

1. Native Tailwind, that is, no configuration changes;
2. Use @apply heavily in CSS files, but still follow the way BEM or other components are organized;
3. Tailwind UI;
4. A large number of custom Tailwind configurations and write custom plugins.

Leo Bauza , “How does Viget’s CSS work?”

The way to use a specific technology may be very different from the way others do, and even if they have the same core, there is little similarity.

The same goes for Bootstrap. You can link Bootstrap from CDN to use the full unmodified version it provides. You can download Sass/JavaScript source files, include them in your own project, and use your own build process. This allows you to customize them, but this complicates the upgrade path. Or you can use Bootstrap from the package manager, which means you are referencing source files from your own build process, but never modifying them directly. Either way, if you are using source code, you can do things like customizing (changing colors, fonts, etc.) and streamlining the parts you want to use.

React and Vue are similar. You can link them directly from the CDN and use them in your browser without the need for a build process. Or they can be the core of your build process and extracted from npm. Or they can be the basis for frameworks like Next or Nuxt.

When you multiply any given single technology in so many different ways, and the number of different technologies used in any given project, it is not difficult to understand why developers experience so differently on projects and why you often hear a lot of people talking in debates.

The above is the detailed content of 'Disambiguating Tailwind'. For more information, please follow other related articles on the PHP Chinese website!