5 ms·
> You're not learning anything valuable by learning Tailwind. 1. You need to know CSS to use Tailwind 2. I learned and understood quite a few of things I rare
by troupo 3y ago
> You're not learning anything valuable by learning Tailwind.
1. You need to know CSS to use Tailwind
2. I learned and understood quite a few of things I rarely use thanks to Tailwind's amazing docs. Docs that are non-existent for CSS
3. I'm reasonably good with CSS, but I could never come up with a consistent and minimal design system that Tailwind offers
That said, to things everyone should read to up their CSS game is Every Layout https://every-layout.dev/ https://every-layout.dev/ and Inclusive Components https://book.inclusive-components.design/ https://book.inclusive-components.design/
- thrixton 3y agoHaving a prebuilt consistent design system that you don’t have to build out for each project, arguing over defaults among the team is a lifesaver.
- emmacharp 3y agoBut you don't need Tailwind for that. A "designsystem.css" file with custom properties would do the trick. Without any added third party tech.
- ethanbond 3y agoWhy should anyone care about adding third party tech? This argument boils down to: “But you don’t need Tailwind for that. You can do more work for a (almost certainly) worse result with a designsystem.css!” Sure you can! Why?
- emmacharp 3y ago(Almost certainly) worse? Haha. Why would it be? If you really want to, you can even use Tailwind's naming for you language file. The thing is, you add complexity to do a job that could be done in the same way without adding complexity and dependencies. Shouldn't we try to justify added complexity through added value?
- ethanbond 3y ago> why would it be? Because most frontend engineers cannot make something as visually appealing as Tailwind’s defaults and most designers cannot make frontend abstractions as ergonomic as Tailwind’s. Now it seems like you’re suggesting just reimplementing Tailwind? Or yes you can have one of your FE engineers and one designer try to dream up your own Tailwind but again: why? Now you’re consuming two people for something that can be achieved by literally zero people and “yarn add tailwind.” It is not at all my objective to “reduce complexity” that sits behind good abstractions. My goal is to ship product and to put as much complexity as possible behind good abstractions and ideally out of my team’s maintenance burden and Tailwind helps achieve all of those. Sure, if Tailwind provided literally zero value I would say you shouldn’t add it to the codebase. But it provides a huge amount of time-value (the best kind!) in my experience, so “there’s a package from the internet” is hardly a consideration whatsoever.
- emmacharp 3y agoIf the Tailind defaults are used in a design language file, wouldn't it be simpler? If it's only a problem of "aesthetics", 20 minutes is enough to use Tailwind's defaults in pure CSS. No need for calling a designer here either. Side benefits include that there is then no need to update any dependencies or library, no need to run a JIT server, no need for a new syntax, no need to wait for implementation of new CSS features, better performance possibilities, etc.
- ethanbond 3y agoJust checking that I understand your suggestion: it’s that you copy/paste Tailwind into a file called “designsystem.css” and then say that you are not using Tailwind? Or are you saying take their design system and use your own syntax for it (so it’s less complete than TW, less well-documented, and less transferable to/from the vast resources of the internet centered around TW)?
- emmacharp 3y agoI'm talking about the design aesthetics included in Tailwind as default. Keep the values and the names if you want. Like this, for example: "blue-500" becomes --blue-500. That's it. This is a far cry from using Tailwind as a whole while keeping the good-looking aesthetics.
- troupo 3y agoI tried to do that once. I decided to skip Tailwind and "just" bring in a few CSS variable that cover what I use. By the 30th variable I stopped. The fact that I had to write significantly more boilerplate in CSS classes on top of that, helped me stop, too
- deprecative 3y agoIf you know CSS why are you using Tailwind which is esoteric CSS but worse? Just use CSS.
- ethanbond 3y agoBecause it’s way, way faster to build with; yields more easily composable, less brittle components; and has a very solid (and rather unopinionated) design system baked in.
- jongjong 3y agoSo glad to read comments like this. I cannot believe my eyes that most devs these days just don't get it and litter their projects with layer upon layer upon layer of unnecessary complexity. I thought a person had to be rational to become a developer but oh my, how wrong I was.
- 3cats-in-a-coat 3y agoEveryone is a developer. This is the paradox of popularity. The theory goes that if you have a large pool of X to select from, then you can select the best of the best, and the quality of your selection will be amazing. But it's exactly the opposite. Small groups are self-selecting for quality and big groups are self-selecting for quantity. O_O English, the universal international language. The one we're speaking here, right now. The worst translators in the world are English translators. Everyone feels qualified to speak it and translate it. Finding a good English translator is like looking for a needle in a haystack. The more "easy languages" and "frameworks" we have, the more "programmers" we also have, and 99.999% of them have the faintest clue what they're doing, but they just keep hitting their keyboard with a hammer, and it compiles and produces interesting results, so they keep doing it. This is also why social networks have an amazing set of interactions when they're new, and in an old social network you have hundreds of millions of users, but no one writes anything interesting, anyone barely reads, and it's full of scams, bots, clickbait and garbage. There's safety in numbers, the saying goes. Not at all. If something is universally popular, and you choose to enter it, get ready for a shitstorm. P.S.: Tailwind is garbage.
- 3y ago
- epolanski 3y agoCare to show one simple example where tailwind's amazing docs cover something MDN or css tricks and others do not?
- troupo 3y agoMDN's docs are amazing, but they are about everything. "CSS tricks" is not documentation (except some very helpful articles). Meanwhile in Tailwind everything is grouped together, can be searched quickly and acts both as quick docs [1] and as quick reference [2]. I personally have become proficient with flexbox by playing with Tailwind classes. [1] E.g. layouts https://tailwindcss.com/docs/display https://tailwindcss.com/docs/display [2] E.g. all the justify-content values https://tailwindcss.com/docs/justify-content https://tailwindcss.com/docs/justify-content