Why is a tailwind palette generator tailwind?

That would require developers to learn CSS… sadly I think they just “learn Tailwind” now

Which is a bit funny because tailwind is just smoke and mirrors CSS. Just write CSS if you're going to use Tailwind. You're already doing that but with a proprietary pseudo set of the syntax.

I once worked with a senior developer who had built out an Ember app, but then mentioned to me that he "didn't know Javascript." I was like… my dude, believe it or not, you are currently using Javascript.

It's not one or the other. I learned CSS by learning Tailwind and using my IDE's preview feature to see what each class did (as well as reading articles, listening to podcasts, etc, but Tailwind was the foundation of my learning). The other day I wrote a tabbed view (like those widgets that show the same example in different programming languages) with 0 JavaScript, using some more advanced features like `:has()` and `nth-child()`.

Not asking for a cookie or anything, but just demonstrating that my understanding of CSS wasn't harmed by learning Tailwind. It was the best path for me as a beginner.

Picking colors I still struggle with. I struggle to find a middle ground between "all gray but readable" (which a client once called "depressing" and compared to Soviet block housing) and "hideously garish". Gray is, unironically, one of my favorite colors, but this view is not popular.