45 likes
·
351 reads
7 comments
This is the content I signed up for Quentin. Very insightful!
Hi, I have seen more and more tailwind lately. I was wondering why you would use text-white instead of style=color:white. I know inline css is bad but it feels like tailwind is just a wrapper around css.
Would love you to hear your opinion
Hi Thomas,
Tailwind is indeed a wrapper (I prefer the term framework at that point because it adds value not just simplify), but also takes in customisation aspects at build time (which makes generated inline-css totally legit to use, since it is totally dynamic with the generated classes/variables ...).
It also offers the variants part (the hover:text-white for example) which is easy to read/use.
Finally, as I am saying in the article, it offers the possibility for a standard across projects and companies. That's where the biggest strength is, like any framework that becomes popular.
Explained well! What are your thoughts on the css-in-js approach?
I like the approach as well, but from a purely logistical perspective, mixing JS and CSS might create more bottlenecks when working with designers/integrators that only familiar with HTML/CSS.
The CSS-in-JS approach is also tricker to organise properly in my opinion ! I overall prefer to separate the two. On the other hands, some developers will find it much more convenient to work with an all-in-one solution 🙂
Hi Quentin,
Awesome write-up buddy!
these resource list is really helpful.
Really insightful, thanks for sharing!