Well for example if you have a style on anchors on a site. If you update the general style (even it its in a class) you have to worry about everywhere that thing is used and whether it will break it. They are all completely coupled.
I mean there are techniques to avoid that like BEM and co, but they rely on you and your colleagues following them, and in my experience are a huge ballache.
Its also sometimes hard to track styling issues down, looking through all of the properties etc. And if you get into SCSS and mixins it slowly gets out of control.
On the flip site with Tailwind, it's all there in front if you and easy to change. If you need to repeat something often, you can just create components / partials with reusable parts.
Yea Tailwind is so good. Yes you have to enter more class names into your html, but the payoff is you don't need to mess about with CSS at all unless you need something very specific.
It also makes it so much easer to progressively update things to a new design, without worrying about 1 change in a CSS file potentially having an effect anywhere.
Coming from someone that uses Linux all the time at work and for personal projects. It's amazing, but the main user experience isn't there yet.
For example I tried Ubuntu Unity on a fresh install for a week or so recently and it was popping up with unknown errors randomly. It also lacks any hotkeys. Software centre seems to have improved but is still buggy. Also there are still occasional issues which make the machine not bootable and hard to sort without stack overflow and some reasonable Linux knowledge.
Ended up swapping back to i3 and just using my old confs.
Which I think is the main issue. There isn't really a good, reliable, simple, predictable desktop experience yet like you get on Windows or MacOS.
Interesting idea but sometimes your projects aren't just a mess of errors and cryptic code. Sometimes they are clean enough, but mainly are just there to learn something, and spending all of the time finishing everything off to try to make it shippable is just a waste of the time that you could be spending on something worth shipping using your new found knowledge.
Although if projects are getting abandoned just because of the mess they are in, that's definitely something to work on.
I mean there are techniques to avoid that like BEM and co, but they rely on you and your colleagues following them, and in my experience are a huge ballache.
Its also sometimes hard to track styling issues down, looking through all of the properties etc. And if you get into SCSS and mixins it slowly gets out of control.
On the flip site with Tailwind, it's all there in front if you and easy to change. If you need to repeat something often, you can just create components / partials with reusable parts.