6 ms·

Is staying in one file supposed to be difficult or something?

• luckylion 7mo ago
  this is grey text from tailwindcss.com, I wouldn't call it easy and readable. <div class="relative before:absolute before:top-0 before:h-px before:w-[200vw] before:bg-gray-950/5 dark:before:bg-white/10 before:-left-[100vw] after:absolute after:bottom-0 after:h-px after:w-[200vw] after:bg-gray-950/5 dark:after:bg-white/10 after:-left-[100vw]"><p class="max-w-(--breakpoint-md) px-2 text-base/7 text-gray-600 max-sm:px-4 dark:text-gray-400">Because Tailwind is so low-level, it never encourages you to design the same site twice. Some of your favorite sites are built with Tailwind, and you probably had no idea.</p></div>
  • what 7mo ago
    That’s actually disgusting.
    • paradox460 7mo ago
      It gets worse Check out the Netlify admin dashboard screenshot in my blog post https://pdx.su/blog/2023-07-26-tailwind-and-the-death-of-craftsmanship/#bigmess https://pdx.su/blog/2023-07-26-tailwind-and-the-death-of-cra...
      • troupo 7mo ago
        There's nothing in Tailwind that makes the craftsmanship dead, and your proposed solution with scoped styles somehow a revival of said craftsmanship. Note how your solution literally depends on a build tool (Vue) to work. Whereas Tailwind can work with no build tools (tailwind build tools removes unused classes, and that's mostly it). And then you go: --- start quote --- Juniors still come along and just do margin: 13px. In tailwind, they do m-[13px]. No difference. At least with CSS its centralized. --- end quote --- When your scoped CSS example is literally decentralized per-file CSS that has `margin: 5px` in it. That gets compiled into a meaningless `class-678x8789g` by the build tool. > The people I've seen who are most excited over tailwind are generally those that would view frontend as something they have to do, not something they want to do. Tailwind is the product of its era: where even sites are composed out of components. That is, this separation of concerns: https://x.com/simonswiss/status/1664736786671869952 https://x.com/simonswiss/status/1664736786671869952 As a comparison, here's Youtube's expertly crafted CSS (which is actually an improvement over their original 6B file). Note how much endless repetition there is: https://www.youtube.com/s/_/ytmainappweb/_/ss/k=ytmainappweb.kevlar_base.D3GEurry95Y.L.W1.O/am=AACAAIAAAg0/d=0/br=1/rs=AGKMywHlqLEnoES9HlRgWKxLMqdaAP827Q https://www.youtube.com/s/_/ytmainappweb/_/ss/k=ytmainappweb...
      • UqWBcuFx6NV4r 7mo ago
        [flagged]
  • halfcat 7mo ago
    In my editor this looks like this, with an extension like Tailwind Fold or Inline Fold: <div class="..."> <p class="..."> Because Tailwind is so low-level, it never encourages you to design the same site twice. Some of your favorite sites are built with Tailwind, and you probably had no idea. </p> </div>
    • dwb 7mo ago
      Ok, and how does it look when you want to read or edit the “classes”?
      • dagi3d 7mo ago
        yeah, Tailwind feels to me like a "write-only" solution.