3 ms·

Tailwind * tries * to resolve this, but is probably just a different bird's nest.

• PaulHoule 4y ago
  Frameworks are going from the frying pan to the fire. There are numerous React frameworks that supply a "widget set" either of web page elements, UI controls or both that work out of the box. If you (your client, your employer, ...) like the way these look out of the box they are a great way to build something quickly and not have to understand the underlying CSS. If you are required to customize the look, however, or you want to combine components from various sources and have them look consistent you have to understand all the concepts of the frameworks, the frameworks the frameworks depend on and CSS.
• vehemenz 4y ago
  Tailwind is a bird's nest in one place instead of a bird's nest in two places with hidden abstractions.
• k1w1 4y ago
  The problem with Tailwind is that it is write-once code. You don't get any leverage. Ideally as you write more code you get more reuse and writing future code becomes faster. In theory CSS classes act like this too. As you have more (well designed) CSS classes then writing future CSS becomes easier because you can reuse the past work. Tailwind breaks this benefit that by encouraging you to write your CSS with glorified styles.
  • whstl 4y ago
    Well, tailwind itself is very reusable, probably the epitome of reusable CSS. And code that uses Tailwind is reusable as long as you use components (React, Vue, Svelte, WebComponents, CSS components with @apply, it doesn't matter). Those are reusable. Trying to use Tailwind without components, in a CSS-garden style page for example, is just trying to fit a square peg in a round hole. It's just the wrong tool for it.