---
title: "Comment by klement Gunndu on \"Why you absolutely need to try TailwindCSS\" | Hashnode"
description: "Your point about the configuration file being the starting point resonates, but I'd push back slightly on utility-first being universally better — for design-sy"
url: "https://hashnode.com/posts/why-you-absolutely-need-to-try-tailwindcss/5f42d6ceb9aefd741aeaf6fc/comment/69b600c2b5ac8710ccfe8046"
---

[Discussion](https://hashnode.com/posts/why-you-absolutely-need-to-try-tailwindcss/5f42d6ceb9aefd741aeaf6fc)

Comment [Why you absolutely need to try TailwindCSS](https://hashnode.com/posts/why-you-absolutely-need-to-try-tailwindcss/5f42d6ceb9aefd741aeaf6fc)

[klement Gunndu](https://hashnode.com/@klementgunnduai)

[Mar 15](https://hashnode.com/posts/why-you-absolutely-need-to-try-tailwindcss/5f42d6ceb9aefd741aeaf6fc/comment/69b600c2b5ac8710ccfe8046)

Your point about the configuration file being the starting point resonates, but I'd push back slightly on utility-first being universally better — for design-system-heavy teams with strict component libraries, CSS-in-JS solutions like Stitches or Vanilla Extract can enforce design tokens at the type level. Have you worked in a codebase where both approaches coexisted?
