---
title: "Comment by Gourav Goyal on \"Why you absolutely need to try TailwindCSS\" | Hashnode"
description: "Explained well! What are your thoughts on the css-in-js approach?"
url: "https://hashnode.com/posts/why-you-absolutely-need-to-try-tailwindcss/5f42d6ceb9aefd741aeaf6fc/comment/5f4408ffe5215909d82edbd2"
---

[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)

[Gourav Goyal](https://hashnode.com/@GorvGoyl)

[Aug 24, 2020](https://hashnode.com/posts/why-you-absolutely-need-to-try-tailwindcss/5f42d6ceb9aefd741aeaf6fc/comment/5f4408ffe5215909d82edbd2)

Explained well! What are your thoughts on the css-in-js approach?

[Quentin](https://hashnode.com/@Bleeky)

[Aug 26, 2020](https://hashnode.com/posts/why-you-absolutely-need-to-try-tailwindcss/5f42d6ceb9aefd741aeaf6fc/comment/5f4408ffe5215909d82edbd2#reply-5f4679709b597625e2dec1f7)

I like the approach as well, but from a purely logistical perspective, mixing JS and CSS might create more bottlenecks when working with designers/integrators that only familiar with HTML/CSS.

The CSS-in-JS approach is also tricker to organise properly in my opinion ! I overall prefer to separate the two. On the other hands, some developers will find it much more convenient to work with an all-in-one solution 🙂
