4 ms·
My best argument against it is whatever the learning curve, you're better served just spending that time learning to write CSS instead.
by pupppet 4y ago
My best argument against it is whatever the learning curve, you're better served just spending that time learning to write CSS instead.
- super256 4y agoWhen you pick up tailwind, you will automatically learn vanilla CSS along the way.
- Bilal_io 4y agoI like Tailwind, but I am not sure I'd recommend it to someone without prior experience and deep understanding of CSS. In my opinion, abstractions rarely teach us the underlying layers of a technology.
- super256 4y ago> I like Tailwind, but I am not sure I'd recommend it to someone without prior experience and deep understanding of CSS. In my opinion, abstractions rarely teach us the underlying layers of a technology. I started with Tailwind and as I learned CSS along the way. Obviously people will look up stuff on MDN when they are stumbling on terms they didn't know about. The tailwind docs + tw-intellisense plugin [1] are pretty good, too. Especially since the extension shows the raw CSS behind the abstraction when you hover over a class name. [1] https://marketplace.visualstudio.com/items?itemName=bradlc.vscode-tailwindcss https://marketplace.visualstudio.com/items?itemName=bradlc.v...
- CapnCrunchie 4y agoMy understanding of CSS has gotten a lot better from using Tailwind.
- postalrat 4y agoHave you reached a stage where you no longer feel its a good idea or are you sticking with it? I considered using it for a few projects but once I start I feel it too much work with no payoff.
- nisegami 4y agoSame here. The CSS that each Tailwind class corresponds to is very visible in the documentation itself.
- terminal_d 4y agoThis has been my experience as well. Tailwind is a good pair of support wheels, but it gets annoying after a while, and is difficult to maintain long-term.
- greenhatman 4y agoWhat make it difficult to main long term for you?
- hbn 4y agoIt's not a replacement for CSS, it's an extension of it. You shouldn't use Tailwind if you don't already know CSS.
- pupppet 4y agoI'd be very surprised if there are many devs with a deep understanding of CSS using Tailwind.
- jmull 4y agoWell... you can bumble through using tailwind without understanding it much in the same way you can bumble through using CSS without understanding it much. There are plenty of people bumbling through with both. But understanding the CSS is needed to use it reasonably well.
- danielvaughn 4y agoI'm sorry but this is just a crazy thing to say. You cannot use Tailwind without understanding CSS. Take the example `block`. Ok so a junior FE dev is supposed to use this class without understanding CSS? How?! It just maps to `display: block;`. It hides literally none of the complexity.
- pupppet 4y ago>It hides literally none of the complexity. If it didn't hide any of complexity you'd be writing CSS.
- danielvaughn 4y agoNope, it saves me (a) keystrokes and (b) design effort. The restricted subset of color options, for example, lets me use a predictable color system out of the box without having to think about it. It's not about removing "complexity" in the sense of understanding how CSS works.
- 4y ago
- greenhatman 4y agoHard disagree on that one. You can learn Tailwind in an evening.