4 ms·

Yes. Much more than doing this via a number of detached and separate CSS classes defined in different files, with colliding rules and all the fun that goes with

by orf 3y ago

Yes. Much more than doing this via a number of detached and separate CSS classes defined in different files, with colliding rules and all the fun that goes with this. Or better yet, inventing enough small composable utility functions to work around these issues until you might have well have used tailwind. When you say “does this look maintainable”, what you should be saying is “does this look maintainable compared to this other thing”.

darajava 3y ago
I’d love to make a simple html skeleton and basic css rules to show a comparison but I don’t have the time.
- orf 3y ago
  You’d need to build a site with multiple pages, with multiple developers and lots of concurrent changes. Then you’d realise why people don’t use raw CSS
  - darajava 3y ago
    I use raw CSS. I just scope it to the component level and I've never had a problem on any of the projects I've worked on. I do tend to avoid absolutely massive projects but I've worked on plenty of fairly big codebases and there is no problem as long as the CSS is scoped well using CSS modules. Inline styles are awful for maintainability and readability of the html, which is an important semantic description of your content.
- haswell 3y ago
  > but I don’t have the time And this, to me, is why Tailwind is so popular and why I find it valuable. Despite looking a bit verbose at first, it’s pretty easy to pull together some pretty advanced pages without having to invest much time at all. And the time saved only increases with more proficiency/familiarity with the available classes. Things very quickly “just work”, and the conventions apply pretty uniformly.
  - _wbrb 3y ago
    It would probably take me 20 minutes or so, and would be very maintainable and not make anyone's eyes bleed. I'm not willing to put that 20 mins in to prove my point, but I am certain that the unmaintainable code vomit which they have as an example on their website took much longer than that.

by orf 3y ago

darajava 3y ago

I’d love to make a simple html skeleton and basic css rules to show a comparison but I don’t have the time.

orf 3y ago
You’d need to build a site with multiple pages, with multiple developers and lots of concurrent changes. Then you’d realise why people don’t use raw CSS
- darajava 3y ago
  I use raw CSS. I just scope it to the component level and I've never had a problem on any of the projects I've worked on. I do tend to avoid absolutely massive projects but I've worked on plenty of fairly big codebases and there is no problem as long as the CSS is scoped well using CSS modules. Inline styles are awful for maintainability and readability of the html, which is an important semantic description of your content.
haswell 3y ago
> but I don’t have the time And this, to me, is why Tailwind is so popular and why I find it valuable. Despite looking a bit verbose at first, it’s pretty easy to pull together some pretty advanced pages without having to invest much time at all. And the time saved only increases with more proficiency/familiarity with the available classes. Things very quickly “just work”, and the conventions apply pretty uniformly.
- _wbrb 3y ago
  It would probably take me 20 minutes or so, and would be very maintainable and not make anyone's eyes bleed. I'm not willing to put that 20 mins in to prove my point, but I am certain that the unmaintainable code vomit which they have as an example on their website took much longer than that.