3 ms·
In a recent thread someone explained Tailwind was best used with component frameworks, and that made it make a lot more sense and I could see the appeal.
by PrimeMcFly 3y ago
In a recent thread someone explained Tailwind was best used with component frameworks, and that made it make a lot more sense and I could see the appeal.
- MrPatan 3y agoStill can't see it. Once you do components CSS gets much simpler, what's the point of a layer on top?
- code_runner 3y agoIt’s actually one less layer. My layout and styling are finally together, and well documented. I don’t mean in the same file like a .vue file. I mean they are TOGETHER.
- timeon 3y agoIt is easier to write CSS with Svelte.
- code_runner 3y agoIt’s easier to poop rainbows with unicorns.
- seedboot 3y agoIt's easier to verb with nouns.
- progx 3y agoI disagree, tried it with a small custom component lib in our company. It was a huge overhead to add options for e.g. a button-component. You can use Tailwind on top level and it is easy. But as soon as you have complex components with sub-elements, the styling gets really complicated. It was easier to add component specific classes and define the css within the component. You call then the component with the classname.