People who just write SCSS don't even think about it.
Engineers learn to work with it due to that simple fact.
It's OK tbh, and it's easily interoperable between stacks so not really hard to pick up and useful if your project already uses it.
I tried to fight it at first, but I've only seen it being used more and more. Why fight the stream if there's no good reason for it?
Why jump tool chains when you already have more than enough on your plate to keep up with?
I watched a conference presentation last week from a front-end person who talked about FE design. He pulled up a slide on bootstrap and said "if you use bootstrap, everything will end up looking like twitter. your login page won't be able to be creative, you'll just look like every other login page".
I had to push back at the end of the presentation with some BS support. I don't use it much any more, but the obvious misinformation about bootstrap continues in 2023, and it's bothersome. FWIW, the presenter said "oh yeah, you're right, and it can be used well, but some people just use the defaults".
Separately, my experiences with tailwind have been less than exciting. Perhaps if I spent the $300+ on 'premium tailwind components' I'd be more on board?
> easily interoperable between stacks so not really hard to pick up and useful if your project already uses it.
And if I don't use it? I get a fair amount of pushback from colleagues sometimes for not jumping on the 'newest' things. Spoiler: I don't deploy many projects with docker either. Is that 'fighting' it? Or just using other established/tested/documented tools and proceses to get a job done?
For an app I may use bootstrap as it is a framework with bigger blocks.
They literally wrote the book on good design[1]
Besides, I'm not saying I think it's a fundamentally bad design, I'm saying those voices are drowned out by the people on-board with it - for a great example, consider how you just came into the conversation, squished the nuance I was discussing, and gave hyperbolic praise to their book just because you like their tool.
These can be applied without the use of tailwindcss.
Use of the framework tailwindcss has nothing to do with the book.
The framework itself goes against the intended use of css. It ignores the power of the cascade and leads to a pile of incomprehensible css repeated over and over again.
It is convenient and unreadable at the same time.
Handy if you don’t want to learn css and use it properly and completely unacceptable if you do.
These can be applied without the use of tailwindcss.
Use of the framework tailwindcss has nothing to do with the book.
The framework itself goes against the intended use of css. It ignores the power of the cascade and leads to a pile of incomprehensible
