I think you might be looking at tailwind the wrong way here.
Tailwind does “enforce” separation of concern between styling and content, just in a different way than the separation of html and css.
Consider the utility class m-1 and m-2. What they are supposed to say is that element with m-1 class and element with m-2 class should have different margin, with the m-2 element probably have a slightly bigger one, and every element that uses m-2 class should have the same margin. It doesn’t specify styling at all. The concerns of styling are completely separated into the theming system.
All that the utility class define is the relation between elements. Eg. which elements should have the same margin/color/typography etc... This would also provides consistency in your designs, unlike pure css which allows you to do whatever you want without defining structure and relationships between elements.
I would say tailwind forces you to separate styling concerns out of your content and into your theme. You could probably replicate css zen garden using tailwind theming system.
Nvidia's DLSS[0] seems to be pretty successful in achieving its goal, which is to allow games to render on lower resolutions without sacrificing too many details.
From what i know, their CI offering tries to aim for very quick build times. Quick as in quick enough to actually allow dynamic looking website to be built with gatsby statically (eg. site rebuilt on every user post). Even their pricing reflects this, they charge by how many times the site is updated, regardless of build time.
I think that looks like a pretty hard problem, i wouldn’t call their CI simple.
You probably need to go back to the dating site multiple times until you finally found "the one". Exchanging numbers and using the dating site service, again and again, multiple times.
Whereas when you're looking for a maid, you probably only need to exchange number once, and that maid will probably suit your need just fine for a really long time.
His venture successfully built reuseable rockets that could lower the cost of spaceflight significantly. This would allow more people to do more things in space. Which could accelerate technological advancement in the space sector.
This is something no one else have been able to do up until recently. I would at least consider that as a notable progress.
Tailwind does “enforce” separation of concern between styling and content, just in a different way than the separation of html and css.
Consider the utility class m-1 and m-2. What they are supposed to say is that element with m-1 class and element with m-2 class should have different margin, with the m-2 element probably have a slightly bigger one, and every element that uses m-2 class should have the same margin. It doesn’t specify styling at all. The concerns of styling are completely separated into the theming system.
All that the utility class define is the relation between elements. Eg. which elements should have the same margin/color/typography etc... This would also provides consistency in your designs, unlike pure css which allows you to do whatever you want without defining structure and relationships between elements.
I would say tailwind forces you to separate styling concerns out of your content and into your theme. You could probably replicate css zen garden using tailwind theming system.