3 ms·
So this is where Tailwind comes into play. With TW, you don’t need to any custom properties. They include base stylings and preflight styles that fix and reset
by hoofhearted 4y ago
So this is where Tailwind comes into play. With TW, you don’t need to any custom properties. They include base stylings and preflight styles that fix and reset just about any browser quirk or bug. The end result is a consistent styles that look and function exactly the same on any device or browser.
There are hundreds of little tiny css style rules and fixes for a perfect website, and you have to remember them all. Tailwind has done all of that, plus a bunch of more.
Their utility classes are their biggest feature in my opinion. Just the ability to set dark mode styles inline with my light mode styles seal the deal for me alone.
- emmacharp 4y agoAgain, I agree the base stylings etc. I do the same in each of my project using pure CSS specifically because I don't want to remember them all. So I have all the same kind of files, and change the design tokens accordingly. The only difference is I configure in CSS whereas you configure in JS. You can bundle it all and keep reusing the same files as you would do in Tailwind.
- hoofhearted 4y agoYeah, it’s pretty much the same difference. For someone starting a brand new app from scratch, they might want to lean on existing css design token libraries. Design tokens aren’t anything new; Bootstrap has been using them for margin for years. mr-1 mt-2