3 ms·
totally agree with that. Tailwind is a crutch but a real bad one (coming from someone that used it extensively the past 2 years).
by sabbaticaldev 2y ago
totally agree with that. Tailwind is a crutch but a real bad one (coming from someone that used it extensively the past 2 years).
- vehemenz 2y agoI don't understand why people think Tailwind is a crutch. It's a tool that uses low level abstractions to build things quickly and lends itself to easier maintenance over time. It has its limits, just like high-abstraction CSS or other frameworks have. It's a bit like saying a van is a "crutch" when you take your family on vacation and that "really" you should be using a bicycle with a trailer on it.
- sabbaticaldev 2y agothat’s the worse comparison someone could think of. if tailwind is a van, CSS is a bus and your family has 40 people.
- vehemenz 2y agoI don't think you understood the analogy. CSS is the language that Tailwind uses. CSS is the language that SCSS is based on. CSS is what other frameworks use. CSS is what the browser interprets for styles. Tailwind is a methodology and a framework. So, it only makes sense to compare other methodologies or frameworks. "Just CSS" isn't a methodology, though non-web folks often think it is. What they probably mean, most of the time, is a certain brand of high-abstraction CSS made popular in the early 2000s. This way of doing things is 3-4x slower (conservatively) than Tailwind and is more difficult to maintain long term. Of course, it's possible to mix and match the best features of CSS with a methodology that reigns in these problems, and that's what I'd advocate people do. But generally Tailwind can get you 90% of the way there.