News for hackers. Stuff that matters.
Re:Tailwind CSS v3.3 by pcthrowaway on Wednesday March 29, 2023 @12:05PM (#35359211)
If you name your own tokens, then other people coming to the project have to learn to apply the same set of tokens correctly, and may even end up reinventing the same ones with new names. In fact, you might even do that (well, it sounds like you might not, but I certainly would, and have)

Tailwind is just that, but unified across all projects, with better tooling (VS code integration, tree shaking, lighter css files)

Re:Tailwind CSS v3.3 by hoofhearted on Wednesday March 29, 2023 @03:01PM (#35361684)
PC, is that you?

I’ve been working towards emailing you to ask if I could upgrade patrickcollison.com

Re:Tailwind CSS v3.3 by pcthrowaway on Wednesday March 29, 2023 @03:12PM (#35361844)
Since this is an anon account, I have a policy of neither confirming nor denying being any person, real or fictional.
Re:Tailwind CSS v3.3 by emmacharp on Wednesday March 29, 2023 @04:01PM (#35362579)
You can use the same standardized nomenclature in CSS if you want it to be "compatible" with Tailwind. Nothing wrong here.