41–50 of 300 posts
Earlier quoted context omitted.
"People who know these things think tailwind is a travesty" Sounds like people don't like changes to things that they are used to. Overall Tailwind really does make styling cleaner.
It makes your job easier at the expense of the quality of your product.
Here‘s a nice green example button, written out of my head during my holidays: rounded p-2 border text-green-800 bg-green-100 hover:bg-green-200 active:bg-green-300 border-green-200 hover:border-green-300 active:border-green-400
It‘s long but somehow it‘s easy, readable, customizable and consistent. The limitations are still there though, just think of transitions and animations.
Personally, I would also be happy if inline styles wouldn‘t be with their limitations, but that entirely another topic.
I presume the use of so many divs is a stylistic choice and not a requirement?
Im sorry but I don’t understand how anyone can look at that and think it’s a good way to build UIs. I’m almost certainly in the wrong, considering how popular this library seems to be getting, but holy heck that looks like a tedious mess to work with. It’s like you have to learn every raw CSS selector, and then also learned how it’s represented in Tailwind, and then scatter that all over your markup.
Completely agree with you. I greatly prefer something like PicoCSS ( https://picocss.com/ ) which tries to use plain HTML5 as much as possible.
Am I only one that feeling like code readability is a bit gross?
A named CSS class can contain any definition and even if you are certain of those definitions, they can change depending on what the element is contained within.
For someone who usually avoids divs in favor of semantic tags, that many divs makes me uncomfortable ;-) I presume the use of so many divs is a stylistic choice and not a requirement?
Earlier quoted context omitted.
> It’s like you have to learn every raw CSS selector, and then also learned how it’s represented in Tailwind, and then scatter that all over your markup. In my experience, tailwind is pretty close to the real CSS properties. What I found to be wonderful and freeing about it is that it stops the middle step of engineering and naming classes and naming elements with class names and let's you just do styling. There's al…
CSS has special syntax for media queries, hover states, dark mode etc. If anything, once you are into it Tailwind is far more "guessable".
Is there a VSCode plugin that help you do something like this: when I type text-20px it will try to find the closest class e.g. text-sm automatically?
You can also do text-[20px] if you really need that specific size.
Im sorry but I don’t understand how anyone can look at that and think it’s a good way to build UIs. I’m almost certainly in the wrong, considering how popular this library seems to be getting, but holy heck that looks like a tedious mess to work with. It’s like you have to learn every raw CSS selector, and then also learned how it’s represented in Tailwind, and then scatter that all over your markup.