You can agree or disagree with the paradigm -- but if you disagree, there really is no point in using Tailwind :)
You can agree or disagree with the paradigm -- but if you disagree, there really is no point in using Tailwind :)
First, Tailwind encourages you to use apply to build reusable components,
second, Taking building blocks from a generator like the one posted here, makes at least to me more sense than it would be for Bootstrap: You see a component and can (thanks to utility classes) see how it's built and change the appearance relatively fast. With Bootstrap you would basically just add a component class and that's it - customizing is more complex then.
On a recent episode of the Full Stack Radio podcast [2], Adam talked about his own upcoming Tailwind UI release and said that he hoped the utility class design of Tailwind would enable people to use the predesigned components as a starting point and easily customize them, should they desire.
[1]: https://www.tailwindui.com/ [2]: http://www.fullstackradio.com/123