Assuming that we're talking about 3 systems where the html is exactly the same between them, and we just want to add a single class on the outer element in order to style the whole component. I can do that with Tailwind.
Yes what you're missing is the hypothetical scenario of using 3 full blown CSS frameworks that apparently share the exact same HTML structure for all their components, which we all know is a farce.
Jared here is just trying to make up bunk reasons for why he feels his superiority complex about CSS is best way.
Yes, your ".box" example is 100% tied to Tailwind. Remove Tailwind from your build process, and that stylesheet is broken. So you can transition sites to Tailwind, but transitioning a site away from Tailwind proves extraordinarily difficult.
Wait, that was the challenge though. We were swapping away from Tailwind so another css framework could style the box. Now you want to keep Tailwind? You can have that cake if you want it. Just render the output one time and link to the rendered css. Itβs cleanly crafted css that could have been written by hand.
Assuming that we're talking about 3 systems where the html is exactly the same between them, and we just want to add a single class on the outer element in order to style the whole component. I can do that with Tailwind.
I'm evidentially missing something here.