Comments by "" (@diadetediotedio6918) on "Is Tailwind really the right default?" video.

  1.  @bangunny  Nah, I think this is a misconception. You can use tailwind before knowing CSS, and use your tailwind knowledge to use CSS better, or it can be the other way around: with your CSS knowledge you can know how to use tailwind better. In principle, this is possible because tailwind is very descriptive, it says to you what it is doing, "bg-xxx" is clearly about a "background color", "w-xxx" is about "width", "pb-xxx" is about "padding bottom", etc... you learn by the naming and by the experience when using the tokens. After that you will use CSS, and you will start discovering there are those same keywords but in an "extended form", so the knowledge is very transferable.
    8
  2.  @paragateoslo  it is called one of the hardest parts of programming for a reason. Naming IS difficult, the fact that you don't see it is concerning, but excusable. Because naming is a problem of syntax, semantics and readability, the more you need to name things the more you need to be careful to not make your code ambiguous or overly verbose, you also need to think on non-trivial names or the problem will only be exacerbated.
    3
  3. HTML + CSS are a literal abstraction, tho. There's no point in criticizing a tool that does this some little more.
    1
  4. @ Let me get this sorted out here: If you are not doing more than one thing in CSS, you are just reinventing tailwind. There's no single world where you are not making an utility class library if you are not applying different styles to your elements in classes that do more than one single specific thing about the styling. In this sense, sure, the name IS the thing it does. Naming is hard because usually things don't do "one single specific and descriptive thing" as this in impractical for many cases.
    1
  5. @ Containers are not doing "one thing", unless you are talking about something very specific. But at the moment you have: color: ...; background-color: ...; border: ...; border-radius: ...; width: ...; height: ...; ... which is pretty normal stuff for classes in CSS, you are already [doing more than one thing] regarding that class, and the naming is now a problem.
    1