引用一下 material ui 的文档说明 tailwindcss 解决的问题https://mui.com/system/basics/#problem-solved
1. Switching context wastes time.
There's no need to constantly jump between the usage of the styled components and where they are defined. With the system, those descriptions are right where you need them.
2. Naming things is hard.
Have you ever found yourself struggling to find a good name for a styled component? The system maps the styles directly to the element. All you have to do is worry about actual style properties.
3. Enforcing consistency in UIs is hard.
This is especially true when more than one person is building the application, as there has to be some coordination amongst members of the team regarding the choice of design tokens and how they are used, what parts of the theme structure should be used with what CSS properties, and so on.