84 karma · joined March 14, 2019
Some comments:
- It's very easy to integrate Sass with Tailwind. You can import the Tailwind classes just like you would Bootstrap: https://tailwindcss.com/docs/using-with-preprocessors#using-...
- You are also allowed to write semantic classes as well: https://tailwindcss.com/docs/extracting-components
I would argue the main point would be you can rapidly build interfaces... like really fast. I worked on a proposal for a client using Tailwind a month ago and we smashed out a whole website in a week. We ended up "extracting components" like buttons and cards and stuff that we found was being reused a lot (kinda like Sass).
As opposed to Styled-Components, the Tailwind classes are very valuable for designers who want to prototype live in the browser.
Also, you were complaining before about design consistency but I would argue that Tailwind allows for very high design consistency. I work with armies of outsourced developers of varying skillsets and I honestly don't trust a lot of them to write clean CSS at all. With Tailwind and Tailwind design tokens, the army of outsource developers are encouraged to work with the design tokens (as opposed to yolo'ing 3px !important everywhere).
One component having mr-4 and another having mr-3 is chill if that was the designer’s intention. If not, then it should be picked up during design review and easily fixed (since you end up really only having to pick from like a few values).
If you really like how Angular 1 worked (writing templates instead of JS to represent DOM) then Vue is a great choice.
> An avid deforester, Bolsonaro has jokingly nicknamed himself “Captain Chainsaw.”
An alternative article from The Guardian says that he rejects that term?! https://www.theguardian.com/world/2019/aug/07/bolsonaro-amaz...
However, you can see just how popular React is by number of npm packages that depend on it: https://github.com/facebook/react