Instead it could really use a lot more explanation on how it works. If you make comparisons make sure they are fair. The image "JavaScript mixed together" and "Strict separation of concerns" is just comparing apples with oranges. Multiple times in the docs it compares a huge complicated JSX like component and replaces it with 3 lines of html and 3 lines of css. I don't believe that it does the same thing.

Some of the claims are strange. It praises standard HTML but apparently you have to use some custom Markdown syntax to write it. How does that add up? And on top of that it also introduces new syntax for loops and variables.

This could all work perfectly fine. But my suggestion would be to talk more about how it works and what are the advantages and less trying to bring down competitors. It could use less grand claims and focus more on what it really does.

If you fall out of the rat race in the US you are screwed. No job, no insurance, no health care, no house, no car followed by homelessness and drug use. After all that it would take an insane amount of effort to get you back up to the ladder.

I know socialism is the big scary word in the US, but socialist European countries mostly prevent people from falling down the ladder that far and fast and the amount of homeless and drug use is significantly lower over here.

Other people right pointed out to download some e-books.

But maybe with a feedback loop it will improve.

Pretty cool example though to see its limitations.

Vanilla CSS, SCSS, BEM, Bootstrap, Styled Components, different kinds of CSS in JS solutions and I still prefer Tailwind over the other methodologies and libraries because I don't have to think about abstractions and naming things. Abstractions are huge foot gun in frontend development because it kills all flexibility. With Styled Components or similar libraries you have to wrap all your components with all kinds of variants that inherit properties. Composition over inheritance is a huge benefit of Tailwind. The big problem with CSS is the specificity and if you ever worked on a real big project with BEM or vanilla CSS/SASS it will eventually become a huge mess of specificity and more and more specific nesting of class selectors to override other styles that you don't want. With Tailwind you can just add exactly what you want, nothing more, nothing less.

Sure the html is "ugly" but that part is invisible.

It is also very likely your bundle size will be smaller because it only adds the CSS for the helpers that you really used.

Just my 2 cents I guess. People should use what they like.