I used it for a project a few years ago when it was first introduced as a phoenix default. It was OK. My favorite thing about it is all the color and spacing utilities - it definitely sped up initial dev because I didn’t need to make many design decisions.
However, eventually I felt like it was slowing me down. I know vanilla CSS pretty well, so it was frustrating to have to keep looking at TW docs to figure out how to do things.
Then all the repetition of classes started to bother me. I tried making small components for everything, but sometimes it just doesn’t make sense to extract a small piece of markup into a component. It felt like my CSS framework was forcing me to make decisions about how my code was structured. So I started to use @apply more and more. At that point I realized I just wanted vanilla CSS again, but it’d be too much work to refactor everything (maybe now a LLM could do it lol).
Now the first thing I do in a new phoenix project is remove tailwind. I don’t really mind that it’s a phoenix default, but I do wish that the --no-tailwind flag would work correctly (see a topic I opened two years ago: Improve phx.new -no--tailwind? ) . I don’t think phoenix should ship with both tailwind and vanilla styles, but it’d be great if you could at least opt out of adding TW classes everywhere when you do phx.new.
