I too have been wondering if tailwind is worth the time investment for me to learn. I have the Tailwind playground bookmarked which seems useful because of the intellisense. I'm in the same boat in that I think a lot in terms of BootstrapVue and native CSS3, and I'm not sure how much I would have to unlearn things before I fully understand tailwind. And it's not completely clear to me if the benefit Tailwind provides is worth the benefits it throws away: like, I can use a class "border-purple-100" but not "border-purple-150"? Whatever used to be a laundry list in css just got moved into a laundry list of class names in the HTML. Also, the other big tradeoff to me appears that changing the entire theme of a given page will become much more challenging when using utility-first framework (i.e., the class names of each element will have to be tweaked). Maybe someone can convince me otherwise.
Hi, I'm Gregory Brown.
My goal is to help software developers get better at what they do, whether they've been at it for five weeks or fifty years.
(he/him)
About changing the theme of a whole page, I mostly assume that I would be using utility classes to build reusable components in Vue, rather than directly using the utility classes everywhere.
So taking that approach, rewriting the theme for each component would then apply the styling wherever it is used.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I too have been wondering if tailwind is worth the time investment for me to learn. I have the Tailwind playground bookmarked which seems useful because of the intellisense. I'm in the same boat in that I think a lot in terms of BootstrapVue and native CSS3, and I'm not sure how much I would have to unlearn things before I fully understand tailwind. And it's not completely clear to me if the benefit Tailwind provides is worth the benefits it throws away: like, I can use a class "border-purple-100" but not "border-purple-150"? Whatever used to be a laundry list in css just got moved into a laundry list of class names in the HTML. Also, the other big tradeoff to me appears that changing the entire theme of a given page will become much more challenging when using utility-first framework (i.e., the class names of each element will have to be tweaked). Maybe someone can convince me otherwise.
About changing the theme of a whole page, I mostly assume that I would be using utility classes to build reusable components in Vue, rather than directly using the utility classes everywhere.
So taking that approach, rewriting the theme for each component would then apply the styling wherever it is used.