Anyone not using Tailwind in a Phoenix project?

I use it but in decoupled setup. Using Phoenix only for API.

I use it only by default, ie, I make sure everything that comes by default in the framework is working fine t´but then, I override it by set different levels of CSS rules that are called after Tailwind in the CSS file and also by creating specific CSS rules for each project that have precedence over Tailwind. And when defining components I place their Css inside so I create a layered approach where everything just works and if I don’t feel I need to use something different Tailwind defaults just work and when I want my own rules they work in a targeted way.

I don’t use it. I much prefer using SASS.

I used a similar utility library (Bass CSS) 10 years ago, and have since worked on many projects that use Tailwind, and to me it seems like a huge step backwards with its sea of CSS classes that are a pain to reason about and that always seem to result in a non-uniform UI.

It’s possible that some people are using it well, but I haven’t personally seen it and I’m happy using SASS.

Yes, Tailwind can impact performance negatively. As CSS is more than just utility classes, you have to consider how the browser render.

But that is usually only a problem if you’re targeting a more native feeling.

I don’t use Tailwind, nor esbuild…

I prefer [rsbuild](https://rsbuild.rs/) instead. It’s a rust builder, so the speed is good. And it is based on webpack.

Also I don’t really have the choice for css. And I don’t like Tailwind

So I always start my project with –no-assets, and build my own assets pipeline.

One more reason is I need to customize for each client, I don’t want my html to be full of classes, I prefer to customize via css instead.

I understand the reason why it has changed. But it means to avoid using npm, and use a fixed css framework

We use pure CSS at work. Our design system somewhat closely follows Every Layout though we have a few utility classes. IIRC we chose to not go with Tailwind to avoid the whole “Well there is a new thing out now that has these advantages and it’s hard to hire anyone who likes Tailwind anymore” whereas vanilla CSS will never go out of style (unless the web itself is completely overhauled).

Personally, I love Tailwind and am using it in a production project for a client. I also like working with pure CSS, though, which I use on my personal site. I haven’t used anything like SASS or LESS in several years at this point.

I do not see the value of Tailwind. It stands against what CSS should be IMHO. I just write my CSS by hand right now.

I am using beercss and I like it. Its so simple and small. Looks good on desktops as well as mobiles.

That looks nice! If Phoenix should have any CSS framework, it should be one without a build step.

I’ve used Tailwind on several professional projects and I really dislike it.

It’s unfortunate that it’s become a default in so many Elixir projects, where most component frameworks default to use Tailwind while using regular CSS would make more sense and would make it usable in both tailwind and non-tailwind contexts.

Bunding something like pico.css or similar as the default would make more sense with Phoenix IMO, and leave Tailwind as an opt-in rather than an opt-out. (Or just use regular CSS for the components of course.)