3 ms·
Perhaps the point of Tailwind isn't to obviate the need to learn CSS. Which seems obviously true to me, given that if you don't know CSS you can't really use Ta
by llamaimperative 2y ago
Perhaps the point of Tailwind isn't to obviate the need to learn CSS. Which seems obviously true to me, given that if you don't know CSS you can't really use Tailwind very effectively.
There's definitely a 0.1% long tail that's tricky with Tailwind (like this), but 99.9% of app styling is so ludicrously fast in Tailwind as compared to writing raw CSS.
- decremental 2y agoReminds me of a common complaint about ORMs. The easy stuff is easy and the hard stuff is insanely hard. This recent post convinced me to just use CSS again: https://dev.37signals.com/modern-css-patterns-and-techniques-in-campfire/ https://dev.37signals.com/modern-css-patterns-and-techniques...
- krsdcbl 2y agoIt definitely isn't, my point is that it seems to be largely is misunderstood as this being it's main purpose. Tailwind is unquestionably accelerating drafting up a custom UI, and also makes this much more approachable for webdevs unaccustomed to CSS The pitfall of declaring all your styles as strings of shorthands in html atts also might never hit you if your UI doesn't get too complex and/or never needs refactoring - but it hits hard if your codebase had grown to a certain scale over the years, and you suddenly need to change or refactor larger parts of the UI
- paulddraper 2y ago> There's definitely a 0.1% long tail that's tricky with Tailwind (like this) That's the first example on the README. (Though perhaps the author of this project did a bad job as choosing a representative example of Tailwind code.)
- llamaimperative 2y agoRight, because it's a usecase that (allegedly) warrants a totally separate package/plugin. Not much CSS is dependent on reading ancestor state.