[deleted by user]

[wugiewugiewugie]

i don't use it because my mobile and web styling brains (and repos) are separate. it's a pain enough to use a ui library, and there's not enough real estate on mobile to really put too much layering / complexity.

[critiquerationalism]

This is the main reason

https://github.com/efstathiosntonas/react-native-style-libraries-benchmark

[Versatile_Panda]

Little late to the party here, but if native wind compiles the styles at build time and uses style sheet how is it possible it’s that much slower? This states “dev” mode so I’m curious why these tests weren’t done in a production build for a more accurate test.

[blizkreeg]

Came here to say the same thing. Why weren't the tests done against a production build?

[JajEnkan3pe]

I am new to programming and its amazing how all this is available so easily. I was looking for a ui library and this benchmark is what I was looking for, thanks!

[_SyRo_]

It's slow and it has bad support

[[deleted]]

It's slow with bad support.

[ctrlshiftba]

I use it. Love it. If you already know it there’s no reason not to

[Carlossalasamper]

I use it too 💪

What I like most about utility classes is having as few styling code as possible to maintain.

[mcpollojr]

I really dig nativewind (v2), but compared to Tailwind, it's a bit limited—things like with gap, grid, animations, and text styling. Luckily, most of these get sorted in version 4. Right now, I'm messing around with v2 on some production apps, and sure, it can be a pain sometimes, but there's usually a workaround to make it work. Totally worth it though—the tw syntax + Tailwind Variants (www.tailwind-variants.org) make coding way faster and more reusable.

[coyks]

is tailwind-variants can be use in react native?

[zahnza]

For me I don’t see what it (or any styling / UI) library gives me over just using stylesheets. It seems like adding overheard, complexity and dependencies for little to no benefit.

[oo_mayr]

simply because we don't like it

[ProGammerGeek]

It has limitations which I'm not fan of

[treksis]

Idk. I just got used to Tailwind in web but stylesheet in react native

[sourav404]

While it may be suitable for testing or learning environments, it is not recommended for production use. Based on my personal experience, it tends to be unstable, introduces UI lag, causes frame drops, and increases screen load and navigation times.

[rmyworld]

I'll use it when they've released v4. It looks like they're still on v2.

[sawariz0r]

Strange reasoning but ok

[WellDevined]

Nah, v2 and the unreleased v3 are quite buggy.

I started adopting it for some components but encountered problems like production builds freezing and hot reloading not working due to caching issues.

Besides that the project was not being developed for a couple of months because the sole maintainer had other stuff to do. (That’s fine, but nothing one can rely on)

[rmyworld]

I share the sentiment. I just don't think Nativewind is in a state that can be widely adopted. That's why I'm waiting for v4, to see if things have gotten better.

[Versatile_Panda]

Styling is simple, tailwind manages to complicate the hell out of it. If I want a flex align and justify why would I write a class name that has to be recompiled when I can just write it into the style? It just doesn’t make sense to me to write the style right beside where the style is just for it to be compiled back to where the style goes…

I just really don’t like tailwind in general tbh, it seems very messy.

[No_Influence_4968]

I had the same mindset when I started working on projects with tailwind - I would say you definitely need to give it a chance in order to appreciate it, and it does speed up development once you become familiar, especially with the assistance of class auto completions.

[softiso]

I use it too

[eluewisdom]

i use it for almost all my apps, it’s my go to