One of my team members evaluated it to see if it was suitable for one of our projects. We came to the conclusion that it's incredibly heavy, and wouldn't give us the performance we desire from the front-end without some additional work, and without PurgeCSS.

Our thoughts were that it might be great for prototyping and getting things demo-ready, but would need to be removed ahead of any go-live or there would be performance issues.

Check out this cool library my friend built using tailwind. Had loads of fun contributing to this library. It has out of the box ready to use components built using tailwind.

npm install kutty --save

// tailwind.config.js
plugins: [require("kutty")],

<!-- All components in one -->
<script src="https://cdn.jsdelivr.net/npm/kutty@latest/dist/kutty.min.js"></script>

<!-- Single component -->
<!-- Include AlpineJS first -->
<script

Im using TailwindCSS since few months and I almost no more writing any css rules by now. I like the utility first approach that I used already with Bootstrap.
But compared to Bootstrap, I like the fact that it's not coming with pre-defined styled components which are very hard to override. Also tailwind is convenient to extend with custom rules and plugins.
To sum up tailwind will be my css framework of choice for the next few years I think ☺️

I don't particularly like Tailwind. I find it very clumsy to work with. Making animations feels like a hack. It's hard to work with the cascade and to let elements flow with one another.
We used it in a previous job on a very large website. Having the CSSOM practically duplicated in HTML was a pain in the ass. It bloated up document sizes tremendously.
We stuck with it to give our designers the option to click together components in Figma.

I find the comparison between Tailwind and Bootstrap a bit odd. Those two are trying to solve different problems. Tailwind is a way to write CSS, while Bootstrap is a component library. Not that I like Bootstrap, but I find the way it writes its classes way more straightforward.

Not worth being taken seriously? That's like saying Bootstrap isn't worth taking seriously. It's definitely something people should take seriously. Does that mean everyone should use it and nothing else, ever? No, of course not. It's a tool, after all and there is room for more than one tool in one's tool belt and room for different tools on other people's belts too. To each their own, that's what I always say.

For me, I really like it a lot. It fits my "style" (pun and no pun intended.) I don't want a CSS framework to make so many decisions for me but, at the same time, I don't want to have to write CSS over and over again, as I've done that before and it's tedious. Tailwind sits in that sweet spot between too much and too little. It's never in the way and at the same time, it's always there for me when I need it, metaphorically speaking, that is.

The complaint I hear the most is "too many classes in the markup." But this is what I love about it. They are right there where they should be, in my opinion. The classes make a lot of sense, too. And I still have the freedom to use as little or as much as I like. If you know CSS you'll learn Tailwind really fast. Plus, the docs are great when you forget something.

I like a blank slate approach and Tailwind respects that.

Does it fit everyone and every project? Of course not. Will I try to use it with a React Native project even though I know I probably shouldn't and realize it may not be the best tool for the job? Of course I will, because I like it and I want to. But that's me, you do you (or what the boss says, I suppose.)

Tailwind 2.0 looks like a really cool release. I read the whole blog post but, haven't tried it. But I already understand what's available and this without even writing code. It's really that simple, once you've learned it (probably take you a day or less to learn it.)

Anyway, give it a real try on a project and enjoy yourself while doing it. Unless you don't enjoy it, then use something else. That's fine too.

I use Tailwind for all smaller projects to quickly implement some styles. For me, it offers a quick way to implement a basic style. This basic style has been designed and maintained by many developers, which makes it the perfect framework to use when you don't have a brand yet.

Some clients require you to implement their styleguide, but when they don't Tailwind will give you the perfect framework to create something beautiful. At Craftworkz, we create many prototypes, and I feel like Tailwind can be a great help here. Fast and beautiful.

Certainly something to keep an eye on!

I like TailwindCSS. It's way better than libraries like Bootstrap or Semantic, because it's focused on layout. Despite that I don't use it because of two things:

1. I like it to write my own (S)CSS
2. By only using TailwindCSS I will forget how to use CSS or SASS or SCSS So I don't like/recommend working with CSS libraries at all. I write my own reusable sheets like 'columns' or 'viewports', but the main styling is in every web app different.

I also recommend to ALWAYS use PurgeCSS (also without using TailwindCSS)

Well, my only experience with it was being thrown into a project where I had to customize an existing Gatsby site for one-off demos, and on short time frames. After grappling with it a bit, I eventually defaulted to just ripping it out every time I had to work with it.

It seems like it's really effective for fast, greenfield development. However, I found maintaining it to be generally super unpleasant, as I now needed to both a) consider how CSS works, and b) understand the author's personal conventions.

That said, it's extremely popular, so either the hype snowball has reached critical mass, or it genuinely solves real problems for a bunch of people.

My colleague implemented tailwind-like margin / padding in our component library and it’s really improved how we handle components and work with design requirements. I’m still hesitant about styling my whole application this way but for margin / padding rules there’s nothing that is more flexible in my opinion.

I get inspired by Tailwind but then I prefer creating my own CSS architecture using a mix of some methologies:

• ITCSS for architecture
• BEM syntax for naming classes
• Large use of utilities classes avoiding repetition and specificity

TailwindCSS is a game changer! Especially now with TailwindCSS 2 out!

Also, I love their new website and how they showcase the framework:

tailwindcss.com/

Our Forem CSS library is inspired by Tailwinds and I love it...

storybook.forem.com/?path=/story/1...

For me it's the best one. I wish they could add some important components like model, Dropdown, navbar with mobile screen support something like that