I'm a full-stack Software Engineer and Architect. I specialise in front-end niceness, but my daily tasks are mostly about making server less work well and scale within our suit of micro services!
Tailwind has to reinvent everything regular CSS can already do.
Additionally this completely misses the point of tailwind and why its existence is necessary.
I would MUCH rather write inline styles (if it wasn't for the obvious draw backs and issues with specificity) and keep the markup close to the styles so when I look at the code I can tell exactly what it's meant to look like and behave like on the page.
Classes like 'button' or 'button-container' are literally meaningless and I have to go looking for the CSS definitions to find them. CSS-in-JS and Vue.js get closer to this, but still keep the information in a separate place.
There's no denying that Tailwind is hideous.
And this knee-jerk reaction is monstrous blinkeredness due to the doctrine herp, more words bad.
It's a descriptive list of abstracted rules which are easily maintainable over semantic classes in place.
I have a lot time and use cases for CSS variables, I use them for ALL my in-house projects/design systems as a basis for my own stripped back utility class library.
But if you look at tailwind, it also relies heavily on css vars declared in root as a basis for it's extensions for size, color, etc.
So I'm not really sure what the point of this was. Like apples and oranges?
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.
Additionally this completely misses the point of tailwind and why its existence is necessary.
I would MUCH rather write inline styles (if it wasn't for the obvious draw backs and issues with specificity) and keep the markup close to the styles so when I look at the code I can tell exactly what it's meant to look like and behave like on the page.
Classes like 'button' or 'button-container' are literally meaningless and I have to go looking for the CSS definitions to find them. CSS-in-JS and Vue.js get closer to this, but still keep the information in a separate place.
And this knee-jerk reaction is monstrous blinkeredness due to the doctrine
herp, more words bad.It's a descriptive list of abstracted rules which are easily maintainable over semantic classes in place.
I have a lot time and use cases for CSS variables, I use them for ALL my in-house projects/design systems as a basis for my own stripped back utility class library.
But if you look at tailwind, it also relies heavily on css vars declared in root as a basis for it's extensions for size, color, etc.
So I'm not really sure what the point of this was. Like apples and oranges?