6

Tailwind is kinda awesome, loving it.

What's your opinion?

Comments
  • 7
    Inline styles = bad

    That’s my opinion
  • 3
    don't see the point of remembering class names, unless there is some vscode extension to help with that.
  • 3
    It clearly shows that some style values are instance specific rather than class specific and that's not really something that you are currently meant to do in HTML and CSS
  • 3
    @theabbie there is one!
  • 2
    @yehaaw you can combine tailwind classes with the @apply directive into your own classes
  • 2
    @SteffTek

    From my experience with Tailwind, I came to the conclusion, that even if you like the approach of it, the library only works with small projects. Tailwind doesn’t really scale well.
  • 3
    Haven't tried it but I've looked at some introductions and examples.

    I have a hard time getting behind super low level classes. They seem like they're just an abstraction for 1 single line of css.
    Like border-radius-25, that's pretty much inline styling to me...

    And even when it comes to more complex combinations of styles I usually prefer doing that in a style file as I often can use multiple selectors. (Allthough I can see how that's not an option when using highly isolated components)
  • 2
    Looking at the markup in the examples is nightmare fuel
  • 0
    @jiraTicket @ars1 I couln't figure it out myself, but a video from fireship on youtube & the vscode addon helps alot.

    It's definitly not for larger scale projects, but it's fun non the less to just "write". Many things are done automatically in the background, even if most classes are just abstractions of "padding: 4px". ^^
  • 0
    @theabbie Search for tailwind intellisense.
  • 1
    In combination with react, vuejs, etc. it's awesome! Would not recommend it for a "vanilla Javascript" site.
  • 2
    @SteffTek gave it's shot recently and it's better than I expected. As long as I can enclosed commonly used stuff to avoid having a million lines of it.
  • 1
    @ars1 I mostly prototype within my vue files and then export it to my own custom components. It's great! As long as you dont use vanilla JS
  • 2
    Yeah, now I remember: you get the most of Tailwind, if you stick to component approach. No need for OOCSS, BEM, and arbitrary class names! So much compliant with DRY.
Add Comment