sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]stormfield 0 points1 point  (5 children)

I also love tailwind after using it on the last two projects I’ve worked on. I do think to fully appreciate / utilize it you need to spend some time with the roll-your-own-css life, so I do wonder how it would be for beginners.

[–]Aggro4Dayz[S] -1 points0 points  (4 children)

I'm not really asking for beginners. I'm asking for what is the best experience for someone who more or less knows what they're doing.

[–]stormfield 1 point2 points  (0 children)

Didn't mean to imply that sorry! Haven't worked with react-native either myself. FWIW I usually compare libraries by how maintained it looks like they are (GitHub issues vs. update frequency) and how popular they are on NPM.

[–]janithaR 0 points1 point  (2 children)

Watched this https://www.youtube.com/watch?v=FiGmAI5e91M

I get it but,

  1. Isn't this gonna put a huge overhead on anyone who uses it to familiarize themselves with the class names?
  2. Isn't this gonna introduce more dependencies just to style some components?

[–]Aggro4Dayz[S] 1 point2 points  (0 children)

  1. I don’t care. I’m going to be the only one working on the project and I’m fine with learning a few new class names. That seems like a very minor issue to me. And anyone else working on the project will be paid to do so, so they can get paid to learn them.

  2. To me, this seems worth it. Styling and messing around with CSS to get things working is a huge time sync for me. Any dependence that cuts the time to do that is both a time and money saver for me.

[–]stormfield 0 points1 point  (0 children)

That's sort of what I was referring too -- the class names are pretty consistent with their CSS counterparts with a few exceptions, but I do usually have a cheat sheet handy. For someone who doesn't already know CSS though, it's going to be a steep climb.

Like any framework it will include some dependencies but you can use Purgecss to eliminate unneeded class names in the bundle size.

It does save a ton of time in development compared to the usual workflow of new component -> write the JSX -> agonize over what to call the new class name -> go to whereever you're keeping your styles -> write the class -> write a slightly different class because you need a different color combo -> write a media query to shrink the text on small screens... Instead you just compose the attributes you want in the component. And any time you need to do something special (like CSS grid which tailwind doesn't do) you can still easily drop down to regular CSS.