of course i had to reply to the wrong comment, is still can't grasp how this site works lol
1 can't agree. Do you also feel the need to not separate your .js files and write your scripts inlined? I bet you don't. Then why is the css an exception?
2 Takes less time to write. I have to admit, I had never used tailwind but it seems to be as fast as vanilla css or even slower
background:red
bg-red
stuff i need to write in css / tailwind. pretty much the same thing
3 tailwind provides a lot of css properties by default like box shadows, gradients and all.
css also does it! and it's even better i think. what if you want to change the border-radius of one specific element? you can't just use the tailwind class, it's configured to always use the same value, right? you still resort to regular css
I don't know about others but almost 70-80% of my apps is usually js, so I like to have as less other files as possible, specially having multiple Module.css file I something I really don't like to do, though I think it's kind of relative, right?
Once you start using it more and more the process gets faster, I admit that it makes jsx look a bit weird due to the longer class names though.
Tailwind provides methods to use custom value actually, you can just do this or extend the theme as needed by adding to tailwind.config.js.
Again, I would like to say that using vanilla css or tailwind or anything else is completely something a developer decides according to their needs and of course the one that's easier and more productive for them. I have used vanilla css in quite large projects and I still do it, that's the reason I feel like tailwind is much faster because I've been using both of them and it's quite clear which one is more productive for me.
of course i had to reply to the wrong comment, is still can't grasp how this site works lol
1 can't agree. Do you also feel the need to not separate your .js files and write your scripts inlined? I bet you don't. Then why is the css an exception?
2 Takes less time to write. I have to admit, I had never used tailwind but it seems to be as fast as vanilla css or even slower
stuff i need to write in css / tailwind. pretty much the same thing
3 tailwind provides a lot of css properties by default like box shadows, gradients and all.
css also does it! and it's even better i think. what if you want to change the border-radius of one specific element? you can't just use the tailwind class, it's configured to always use the same value, right? you still resort to regular css
am I wrong?
I don't know about others but almost 70-80% of my apps is usually js, so I like to have as less other files as possible, specially having multiple
Module.cssfile I something I really don't like to do, though I think it's kind of relative, right?Once you start using it more and more the process gets faster, I admit that it makes jsx look a bit weird due to the longer class names though.
Tailwind provides methods to use custom value actually, you can just do this or extend the theme as needed by adding to
tailwind.config.js.Again, I would like to say that using vanilla css or tailwind or anything else is completely something a developer decides according to their needs and of course the one that's easier and more productive for them. I have used vanilla css in quite large projects and I still do it, that's the reason I feel like tailwind is much faster because I've been using both of them and it's quite clear which one is more productive for me.
fair, I I'm not saying that tailwind has no use cases, just wanted to know your perspective, thanks