27 pointsby rmykhajliw6 hours ago8 comments
  • rmykhajliw6 hours ago
    I don’t believe the Tailwind approach is a stable, scalable, or reliable solution for large, long-living products.

    It works well for fast delivery, prototypes, and teams optimizing for short-term speed, but over time it tends to spread styling decisions across markup, making the system harder to control, reason about, and maintain.

    • tmnvix4 hours ago
      I agree. But also, on a broader note, I have no desire to introduce node for the sole purpose of some css niceties.

      Coming back a couple of years later to a broken build system when you just want to change a colour is no fun.

  • rahimnathwani4 hours ago
    "Bootstrap takes the opposite approach by limiting flexibility and embedding decisions into predefined components."

    If you choose tailwind, nothing is stopping you from using components. You can choose to use predefined components, or you can create your own. Or some mix.

    • freedomben4 hours ago
      My thoughts too. There's no real reason I can think of that you couldn't build a Bootstrap on top of Tailwind. They're kind of at different levels of the stack.
      • ChocolateGod4 hours ago
        Things like Shadcn are effectively Bootstrap on top of Tailwind.
  • bentocorpan hour ago
    I am missing the point of Tailwind?

    Don't you get the same effect and functionality from simply adding style attributes directly on the elements in HTML?

    Why is that approach considered bad practice, while Tailwind, which is effectively the same – but with shortened names – accepted as common practice?

    As the article states, at least with Bootstrap you are sharing common behaviour with a single class name that can then be modified globally.

  • jaapz4 hours ago
    Ah, time for the pendulum to start swinging back again
  • ricardobeat5 hours ago
    What happens in practice is you use Tailwind with components (React or otherwise), so you build `<Button primary>` using tailwind classes internally; this is functionally the same as the boostrap classes, but can standardize much more than styles.

    It just adds an extra layer of abstraction, which I happen to also find unnecessary.

    • montroser43 minutes ago
      > It just adds an extra layer of abstraction, which I happen to also find unnecessary.

      Can't tell if you're talking about React or Tailwind

  • MK_Dev4 hours ago
    Tell 'em! I also hate React and love Razor, but most don't seem to share that sentiment
  • jdmoreira4 hours ago
    Just use DaisyUI
    • freedomben4 hours ago
      Indeed. Claude jammed DaisyUI into a vibe code weekend project when I wasn't looking, and I've actually been pretty happy with it even now that I have to code myself (AI starts to really suck ass for the last 20%, so I usually take over then, but love the bootstrapping and PoC-ness). Petal UI is usually my preference, though that's only on Elixir LiveView (but that's my stack of choice anyway)
  • ceritium5 hours ago
    Me too