As someone working in this space, it's a huge relief to move away from piles of CSS/SCSS files towards colocating styles with markup.
I went through a very similar story to the author and ended up with the same conclusion. Once I tried it, everything else felt terrible
http://sunsite.uakom.sk/sunworldonline/swol-04-1997/swol-04-...
Webseitenstilzerschütterungsangst?
This feels a bit dismissive. Alipay is the largest payment platform in the world.
After reading the excellent article it hit me, I'm already doing the exact same :facepalm:
<Box mr="4" border="1px solid #ee"... />
There is really no difference, instead of a string with classes I have a bunch of props. Time to look at tailwind again...
It's just easier to do fast proto-typing with various Tailwind classes, and then refactor common sets of HTML tags with tailwind classes, they become reusable React (or Svelte) components.
Separation Of Concerns (HTML <-> CSS) is a LIE. Naming is one of the hardest things in computer science, and folks in the "Separation Of Concerns" camp repeatedly subject themselves to this torture by forcing themselves to come up with "semantic" names instead of just writing the damn styles and seeing which styles get repeatedly used together so that they can be condensed into a class.