News for hackers. Stuff that matters.
Re:Tailwind: style your site without writing any CSS by paulsutter on Friday November 02, 2018 @11:20AM (#18363640)
Easier just to quote the reason he gives:

“With inline styles, there are no constraints on what values you choose... Utilities force you to choose...

You can't just pick any value want; you have to choose from a curated list. Instead of 380 text colors, you end up with 10 or 12.”

Re:Tailwind: style your site without writing any CSS by ealhad on Friday November 02, 2018 @11:47AM (#18363866)
And of course, those colors are fully customizable.
Re:Tailwind: style your site without writing any CSS by jacamat on Friday November 02, 2018 @12:49PM (#18364551)
in what way is that consistent tho?
Re:Tailwind: style your site without writing any CSS by neurotrace on Friday November 02, 2018 @02:05PM (#18365238)
In what way is it not? You'll consistently get 10 or 12 colors instead of getting an inconsistent set of colors, for example.
Re:Tailwind: style your site without writing any CSS by jacamat on Friday November 02, 2018 @05:24PM (#18366904)
But I only want the element to be the color it IS, not a range of colors it could be. Whats to stop a dev using $concrete when they should be using $cloud? or $linkGray instead of $headerLinkGray?

these inconsistencies compound, especially across teams.

Re:Tailwind: style your site without writing any CSS by neurotrace on Tuesday November 06, 2018 @02:00PM (#18393909)
Nothing would stop them from choosing to use cloud vs. link gray but it's far easier to identify and fix those cases than it is to have #CCC, lighten(#CCC, 10%), etc. around the codebase. This doesn't fix human error, just reduces it.