I really like tailwind! I love that I can swap between projects and change things quickly without having to remember what I named things. Or spend time thinking about what to name things. I use single file components so if something is reused, it is put into a component.
A couple of things that also make me like tailwind: It's faster than writing CSS from scratch. Great padding, margin, size, breakpoints and font classes that scale correctly. It means it's easier to keep a design consistent. I don't want to have to think about these things for every application I make.
As for other CSS frameworks. I've used foundation and bulma for a few projects. I felt like I was fighting against the defaults to ensure the site matched the design.
The other reason that I enjoy using tailwind is that I have a figma template with all of the tailwind defaults. This means I can design and translate this into code with minimal fuss and time.
But to each their own. Whatever works for you and your team. I agree that it can feel messy, but clients care about the result, not the source code!
But isn't the original question about readability and understandability for others? Is fine for you to write quick code now but doesn't help anyone else now or later?
One of the points I mentioned was that is was easy to swap between projects that has tailwind, as you don't have to figure out class names etc. If someone has worked with tailwind on one project, then they can easily use it any other tailwind projects. I'd argue it is easier than bootstrap or foundation, because the utility classes are fairly close to CSS property names. However the classes have inbuilt spacing etc.
I found it quicker to learn and much easier to understand others code when editing. That is one of the first things I mentioned and one of the main reasons I use it!
Fair enough, although I guess is a bit like using Vue vs react, not everyone knows how one or the other works. Personally I'm still working up to applying tailwind in the functional elm-like framework hyperapp.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I really like tailwind! I love that I can swap between projects and change things quickly without having to remember what I named things. Or spend time thinking about what to name things. I use single file components so if something is reused, it is put into a component.
A couple of things that also make me like tailwind: It's faster than writing CSS from scratch. Great padding, margin, size, breakpoints and font classes that scale correctly. It means it's easier to keep a design consistent. I don't want to have to think about these things for every application I make.
As for other CSS frameworks. I've used foundation and bulma for a few projects. I felt like I was fighting against the defaults to ensure the site matched the design.
The other reason that I enjoy using tailwind is that I have a figma template with all of the tailwind defaults. This means I can design and translate this into code with minimal fuss and time.
But to each their own. Whatever works for you and your team. I agree that it can feel messy, but clients care about the result, not the source code!
But isn't the original question about readability and understandability for others? Is fine for you to write quick code now but doesn't help anyone else now or later?
One of the points I mentioned was that is was easy to swap between projects that has tailwind, as you don't have to figure out class names etc. If someone has worked with tailwind on one project, then they can easily use it any other tailwind projects. I'd argue it is easier than bootstrap or foundation, because the utility classes are fairly close to CSS property names. However the classes have inbuilt spacing etc.
I found it quicker to learn and much easier to understand others code when editing. That is one of the first things I mentioned and one of the main reasons I use it!
Fair enough, although I guess is a bit like using Vue vs react, not everyone knows how one or the other works. Personally I'm still working up to applying tailwind in the functional elm-like framework hyperapp.