Accessibility Specialist. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
It goes against the whole point of CSS…utilising the Cascade (the “C” part).
It adds loads of replication in your HTML, it requires you to rely on it actually working (lately there have been problems with the JIT compiler causing required styles to be missed) and by the time you learn all the classes you are 70% of the way to learning CSS anyway!
Don’t get me wrong for prototyping it is useful, but in production, if I have a choice, I wouldn’t touch it!
Accessibility Specialist. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
Yeah exactly, sorry it is bank holiday here in the UK so not been on properly to answer.
I use vanilla CSS and a “micro libraries” approach. So if there is a complex component that I don’t want to have to build I will use an off the shelf solution and then adjust the styles to suit the site.
At this stage though I have my own library of patterns that work and are set up to use CSS vars for styling so it becomes more of a copy paste and change 3/4 vars job for 95% of things. 👍
I completely agree! It's so strange to put all the style, design and layout choices back in the HTML document! It's also super unreadable and hard to refactor.
I think tailwind became so popular because it gives developers who do not design/write CSS a quick solution to put some layout into the document without touching a CSS file.
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.
Well I’m going to start a war here but….tailwind!
It goes against the whole point of CSS…utilising the Cascade (the “C” part).
It adds loads of replication in your HTML, it requires you to rely on it actually working (lately there have been problems with the JIT compiler causing required styles to be missed) and by the time you learn all the classes you are 70% of the way to learning CSS anyway!
Don’t get me wrong for prototyping it is useful, but in production, if I have a choice, I wouldn’t touch it!
What do prefer using? Bootstrap? Materialize?
He prefers vanilla css from my understanding
Yeah exactly, sorry it is bank holiday here in the UK so not been on properly to answer.
I use vanilla CSS and a “micro libraries” approach. So if there is a complex component that I don’t want to have to build I will use an off the shelf solution and then adjust the styles to suit the site.
At this stage though I have my own library of patterns that work and are set up to use CSS vars for styling so it becomes more of a copy paste and change 3/4 vars job for 95% of things. 👍
I completely agree! It's so strange to put all the style, design and layout choices back in the HTML document! It's also super unreadable and hard to refactor.
I think tailwind became so popular because it gives developers who do not design/write CSS a quick solution to put some layout into the document without touching a CSS file.