[ComiCSS] Benefits of Tailwind
-
They said that You either hate or love tailwind, and when I first used tailwind I assumed it was just a joke, 'why would they hate this? It's simple to use, remember, build, and it even removes unnecessary CSS that I forget to do...'
Apparently it isn't as simple as that.
-
That's not accessibility.
You think only aria-attributes are accessibility? Most accessible is, what you not need additional tools and interpreters for.
-
You think only aria-attributes are accessibility? Most accessible is, what you not need additional tools and interpreters for.
No, it's of course not just aria attributes. But it's definitely not "how easy can I create user CSS". Accessibility is a term of art, you can't just expand its meaning to whatever you want.
-
you need to know css to use tailwind because it’s basically style= on everything: it’s css with extra steps
Well, it's
classNameon everything
And yes, it's literally CSS utility classes with an extra installation step that you only do once -
No, it's of course not just aria attributes. But it's definitely not "how easy can I create user CSS". Accessibility is a term of art, you can't just expand its meaning to whatever you want.
wrote on last edited by [email protected]Look, if it hinders me in my workarounds for my ADHD while every other framework does less so, then accessibility is worse. Shut up with your trademark gatekeeping bullshit.
Also,
-
Now it is remembering tags for property instead.
Any passable editor nowadays does the heavy lifting for you, you can usually even write the CSS tag you want and it'll show you the options.
-
I was very much against frameworks initially: tailwind, bootstrap etc. However, when I started really building sites & apps using components, I found tailwind made my life a lot easier, so I could easily see and change styling while writing code/html, and it would only affect that component.
Beforehand, I was trying to come up with names for CSS classes all the time, and then I'd change one thing, and fuck up styling on a diff page.
Yep, a component is a good abstraction level, no point in making life difficult by creating and coming up with names for smaller parts.
-
They said that You either hate or love tailwind, and when I first used tailwind I assumed it was just a joke, 'why would they hate this? It's simple to use, remember, build, and it even removes unnecessary CSS that I forget to do...'
Apparently it isn't as simple as that.
I guess some people write code, and some people also read and maintain it.
-
Having never used it before, is it that bad?
It's a nicer syntax for inline styles.
If you want to use inline styles everywhere, it's great.
-
It's a nicer syntax for inline styles.
If you want to use inline styles everywhere, it's great.
It's much more than just inline styles. It's also design constants (e.g. color palettes, sizing etc.) and utilities (e.g.
ring). -
Genuine question : what's wrong with modern vanilla CSS3 ?
Maybe it's because I've used css2 I don't see the point of css frameworks.
wrote on last edited by [email protected]Don’t know about tailwind but I used styled-components and not going back to vanilla css. CSS seems to be designed to be used with HTML, which did make sense back when it was created. Modern web is 99% JS and components composition which does not work well with Vanilla CSS in terms of class name uniqueness, specificity. Also it easy to dumb shit with CSS, like, I worked in the project where we had a lot of legacy global CSS. We had like dozen CSS styles which were adding margin to <label/>, <p> and so on. I mean no classes, just globally. I’ve been forced to add ‘all: unset’ to basically all my new components just to avoid changing global styles and breaking something else. Do not recommend.
-
People fear what seems foreign. Devs want css to be like a programming language and it's not so they're uncomfortable. Or at least this is my unvarnished opinion
For me it's less about fear and more about having a limited budget of time and effort to spend on learning things, so CSS and front end generally gets deprioritized. But that's cuz I'm a back end kinda dev in my soul, lol.
I've seen the good points you've made elsewhere in this thread - I would indeed react very poorly to willy-nilly back end changes and I think you're right that people don't give CSS and visual styling the same degree of professional respect when making changes. And that sucks.
-
I wonder if any colorblind people completely didn't understand this meme
-
Don’t know about tailwind but I used styled-components and not going back to vanilla css. CSS seems to be designed to be used with HTML, which did make sense back when it was created. Modern web is 99% JS and components composition which does not work well with Vanilla CSS in terms of class name uniqueness, specificity. Also it easy to dumb shit with CSS, like, I worked in the project where we had a lot of legacy global CSS. We had like dozen CSS styles which were adding margin to <label/>, <p> and so on. I mean no classes, just globally. I’ve been forced to add ‘all: unset’ to basically all my new components just to avoid changing global styles and breaking something else. Do not recommend.
I tend to build stuff with html css and php only ( all vanilla) and avoid non trivial js like the plague.
I can see your point but for me replacing HTML with js is just wastefull, you leave performance and built in accessibility on the table for a slightly more convenient experience that don't work for me. -
Fair enough. What ui framework(s?) on tailwind do you like?
I like daisyUI because it doesn't have any Javascript
-
I tend to build stuff with html css and php only ( all vanilla) and avoid non trivial js like the plague.
I can see your point but for me replacing HTML with js is just wastefull, you leave performance and built in accessibility on the table for a slightly more convenient experience that don't work for me.Don’t get me wrong, I’d always choose html over js if I could. My problem with css, and web in general, that it’s too fragmented. It’s like those people who are designing css, html, js and browsers didn’t speak to each other whatsoever. So now there is entire industry of js frameworks to glue all shit together. Like, look at the WebComponents. Which supposed to be native, out of the box replacement. So much effort and they still cannot compete, in some cases they simply do not provide basic features needed to build complex UIs. Next time I can choose stack I’ll probably just go with htmx
-
I like daisyUI because it doesn't have any Javascript
Tried it. It was terrible. Reverting.
-
Tried it. It was terrible. Reverting.
To each their own I guess
