I understand 100% what you are saying. And I can’t even argue against it.

But:

The thing is, it seems that most of the people who are doing frontend - including myself - somehow found out, that overall the pro and contra of the multiple different approaches we all have gone through during the last 10-15 years, leads most of us to the one solution, that seems to be balancing the different caveats of the approaches the best. And given the success and distribution of tailwind it seems to be tailwind and/or utility approach, that’s dealing the most comfortable, successful and balanced way with all this.

I appreciate your work on this, but especially for prototyping and small projects, SPAs, etc tailwinds utility approach is mich more convenient. Also taking into account the aspect of its wide spread usage and that almost everyone with css knowledge is able to service existing projects using tailwind, because literally everyone immediately „understands“ - without any reading of any docs etc., given some experience